CVE
X-Road cross-instance config poisoning via federated download
Affects X-Road Security Servers that download global configuration from a federated ecosystem. Fixed in 7.6.5, 7.7.3 and 7.8.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.6.5, 7.7.3, 7.8.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Security Server downloads global configuration from a federated ecosystem The federated ecosystem is malicious or compromised and serves a validly signed SHARED-PARAMETERS part naming the victim's ecosystem
Summary
X-Road software writes downloaded federated global configuration under whichever instance identifier the downloaded part declares, without checking that it matches the ecosystem that sent it. An attacker who controls a federated source and has high-privilege login access over the network can plant a signed configuration as a victim ecosystem's trusted settings, add attacker-controlled trust material, and impersonate members and Security Servers across every ecosystem federated with that source.
Original description
X-Road is open-source data exchange layer software. Prior to .8.2, 7.7.3, and 7.6.5, the Security Server writes each downloaded federated global-configuration part under the X-Road instance identifier declared by the part itself without checking that the identifier matches the source ecosystem that signed and delivered it. A malicious or compromised federated ecosystem can provide a validly signed SHARED-PARAMETERS part naming a victim ecosystem, causing the part to be written as the victim's authoritative shared-params.xml. The poisoned configuration can persist across refreshes, add attacker-controlled trust material, and enable impersonation of victim members and Security Servers across every ecosystem federated with the malicious source. This issue is fixed in versions 7.8.2, 7.7.3, and 7.6.5.
Who should check
Teams running the X-Road Security Server in a federated ecosystem that downloads global configuration from other federated ecosystems
“When a Security Server downloads global configuration from a federated ecosystem”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8/10CVSS 8.0
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Security Server downloads global configuration from a federated ecosystem The federated ecosystem is malicious or compromised and serves a validly signed SHARED-PARAMETERS part naming the victim's ecosystemUpgrade to a fixed version: 7.6.5, 7.7.3, 7.8.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-62340 (X-Road: Cross-instance global configuration poisoning via federated download), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-62340 (entry last updated 2026-11-18):
Affected:
- nordic-institute X-Road: fixed in 7.6.5; from 7.7.0, fixed in 7.7.3; from 7.8.0, fixed in 7.8.2
Fixed versions: 7.6.5, 7.7.3, 7.8.2.
Conditions (all must be true for the bug to be hit):
- Security Server downloads global configuration from a federated ecosystem (source: https://github.com/nordic-institute/X-Road/security/advisories/GHSA-c5gr-pcm6-828r)
- The federated ecosystem is malicious or compromised and serves a validly signed SHARED-PARAMETERS part naming the victim's ecosystem (source: https://github.com/nordic-institute/X-Road/security/advisories/GHSA-c5gr-pcm6-828r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-62340 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62340 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nordic-institute/X-Road/security/advisories/GHSA-c5gr-pcm6-828r
- https://github.com/nordic-institute/X-Road/commit/2bc4673bd1d1dda0f3e7c10236cb1fea7e8847f8
- https://github.com/nordic-institute/X-Road/commit/8e38314df30a54bab3220222c9567a0f9cc6490d
- https://github.com/nordic-institute/X-Road/commit/bd2490c6d68a9cf057b071054187b9c33d4ba9b8
- https://github.com/nordic-institute/X-Road/releases/tag/7.7.3
- https://github.com/nordic-institute/X-Road/releases/tag/7.8.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-62340
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62340"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nordic-institute X-Road
fixed in 7.6.5; From 7.7.0 · fixed in 7.7.3; From 7.8.0 · fixed in 7.8.2
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nordic-institute/X-Road · Advisory GHSA-c5gr-pcm6-828r |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-62340 |
| Record | NVD · CVE-2026-62340 |
| Other links 5 | |
| Repository | GitHub · nordic-institute/X-Road · Commit 2bc4673b |
| Repository | GitHub · nordic-institute/X-Road · Commit 8e38314d |
| Repository | GitHub · nordic-institute/X-Road · Commit bd2490c6 |
| Repository | GitHub · nordic-institute/X-Road · Release 7.7.3 |
| Repository | GitHub · nordic-institute/X-Road · Release 7.8.2 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62340
Is CVE-2026-62340 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A malicious or compromised federated ecosystem can serve a validly signed SHARED-PARAMETERS part that names the victim's ecosystem. This overwrites that ecosystem's authoritative trust configuration and gives the federated ecosystem full, persistent control, including the ability to impersonate the victim's members and Security Servers.Source: github.com
Which versions are affected by CVE-2026-62340?
X-Road: before 7.6.5; from 7.7.0 before 7.7.3; from 7.8.0 before 7.8.2.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are those below 7.6.5, 7.7.0 through 7.7.2, and 7.8.0 through 7.8.1. The bug applies to setups where a Security Server downloads global configuration from a federated ecosystem, so compare the installed X-Road version with these ranges and check whether that download is configured.Source: github.com
How do I fix CVE-2026-62340?
Upgrade to 7.6.5, 7.7.3, or 7.8.2, matching the release line in use.Source: github.com