Skip to main content
Menu
CVEs

CVE

X-Road arbitrary file creation in Configuration Proxy

CVE-2026-63483EUVD-2026-129168Published Updated Summary written by a model

6.6MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 7.8.2, 7.7.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.8.2, 7.7.3.

Summary

X-Road, an open-source data exchange layer, has a flaw in its Configuration Proxy that lets a network attacker with high-level access create new files with attacker-chosen content, without any user action, under the permissions of the non-privileged xroad process. The attacker does this through a malicious or compromised federated global configuration that uses an absolute path or directory traversal sequence, which can poison downstream configuration or write files to other writable locations, but it cannot overwrite existing files.

Original description

X-Road is open-source data exchange layer software. Prior to 7.8.2 and 7.7.3, the Configuration Proxy uses attacker-controlled Content-location metadata from a validly signed federated global configuration part when constructing an output path without verifying that the resulting path remains inside the intended configuration output directory. A malicious or compromised federated ecosystem can provide an absolute path or directory traversal sequence during the normal refresh cycle, causing the Configuration Proxy to create a new file with attacker-controlled content under the permissions of the non-privileged xroad process. The vulnerability can poison downstream global configuration or create files in other writable locations, but it does not overwrite existing files. This issue is fixed in versions 7.8.2 and 7.7.3.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.6/10CVSS 6.6
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 44 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.8.2, 7.7.3.

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-63483 (X-Road: Arbitrary file creation via malicious global configuration in the X-Road Configuration Proxy), 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-63483 (entry last updated 2026-11-18):
Affected:
- nordic-institute X-Road: fixed in 7.8.2; from 7.7.0, fixed in 7.7.3
Fixed versions: 7.8.2, 7.7.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-63483 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63483 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-hqh5-8gwp-w8qw
- https://github.com/nordic-institute/X-Road/pull/3634
- https://github.com/nordic-institute/X-Road/commit/6425df49c173f915c6b450f5559b2fb185a68def
- https://github.com/nordic-institute/X-Road/commit/c528666afbe61d36f8b73ad9a4afe6fdaf5fd573
- 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-63483
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-63483"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • nordic-institute X-Road

    fixed in 7.8.2; From 7.7.0 · fixed in 7.7.3

Evidence 8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-63483

Is CVE-2026-63483 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-63483?

X-Road: before 7.8.2; from 7.7.0 before 7.7.3.Source: cve.now feed data

How do I fix CVE-2026-63483?

Upgrade to a fixed version: 7.8.2, 7.7.3.Source: cve.now feed data

More CVEs