CVE-2026-55390

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

datamodel-code-generator generates Python data models from schema definitions. From 0.59.0 until 0.62.0, XML Schema parsing in src/datamodel_code_generator/parser/xmlschema.py for --input-file-type xmlschema resolves xs:include, xs:import, xs:redefine, and xs:override schemaLocation values outside the input base path, allowing arbitrary local files to be read and reflected into generated models. This issue is fixed in version 0.62.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 29, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

0.62.0

Patch available: koxudaxi/datamodel-code-generator 0.62.0

https://github.com/koxudaxi/datamodel-code-generator/releases/tag/0.62.0
github_commit Patch Available

commit d2d5cecd9fd3 (koxudaxi/datamodel-code-generator)

Patch available: koxudaxi/datamodel-code-generator 0.62.0 (contains commit d2d5cecd9fd3)

https://github.com/koxudaxi/datamodel-code-generator/commit/d2d5cecd9fd3a2a6dbf148bf0740b83a11fc6820
github Patch Available🟡 PoC Available

Arbitrary local file read via XSD `schemaLocation` (`xs:include`/`xs:import`) path traversal, with no remote-ref gate · Advisory · koxudaxi/datamodel-code-generator · GitHub

https://github.com/koxudaxi/datamodel-code-generator/security/advisories/GHSA-442q-2j6p-642g

Vendor Advisories for CVE-2026-55390(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
datamodel-code-generator0.59.0 ... 0.61.0 (6 versions)0.62.0

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 02:16 UTCEG score recompute
  2. 2026-07-30 01:30 UTCEPSS rescore
  3. 2026-07-29 15:24 UTCEG score recompute
  4. 2026-07-29 14:49 UTCEG score recompute
  5. 2026-07-28 22:27 UTCEG score recompute
  6. 2026-07-28 21:29 UTCEG score recompute
  7. 2026-07-28 21:28 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55390?
CVE-2026-55390 is a high vulnerability published on July 28, 2026. datamodel-code-generator generates Python data models from schema definitions. From 0.59.0 until 0.62.0, XML Schema parsing in src/datamodelcodegenerator/parser/xmlschema.py for --input-file-type xmlschema resolves xs:include, xs:import, xs:redefine, and xs:override schemaLocation values outside…
When was CVE-2026-55390 disclosed?
CVE-2026-55390 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55390 actively exploited?
CVE-2026-55390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-55390?
CVE-2026-55390 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55390?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55390, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55390

Explore →

Is Your Infrastructure Affected by CVE-2026-55390?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.