datamodel-code-generator generates Pydantic v2 models, dataclasses, TypedDict, and msgspec.Struct from OpenAPI, JSON Schema, GraphQL, Avro, Protobuf, and raw JSON, YAML, or CSV. From 0.9.1 until 0.61.0, datamodel-code-generator silently dereferences attacker-controlled JSON Schema $ref HTTP or HTTPS URLs in src/datamodel_code_generator/parser/jsonschema.py through _get_ref_body, and the --allow-remote-refs gate can warn instead of blocking, allowing server-side request forgery through src/datamodel_code_generator/http.py. This issue is fixed in version 0.61.0.
CVE-2026-54690
HIGHPre-NVD 8.28.2—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 53(Track)EG Risk 53/100SSVC: Track
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 computedSeverity82% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- 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, github_commit, github_release.
github_release Patch Available
0.61.0
Patch available: koxudaxi/datamodel-code-generator 0.61.0
https://github.com/koxudaxi/datamodel-code-generator/releases/tag/0.61.0github_commit Patch Available
commit 5fdba4a09f2d (koxudaxi/datamodel-code-generator)
Patch available: koxudaxi/datamodel-code-generator 0.61.0 (contains commit 5fdba4a09f2d)
https://github.com/koxudaxi/datamodel-code-generator/commit/5fdba4a09f2d7a9996a504975b7ef7d63e3715bbgithub Patch Available🟡 PoC Available
SSRF in datamodel-code-generator via JSON-Schema `$ref` to HTTP URL (silent by default) · Advisory · koxudaxi/datamodel-code-generator · GitHub
https://github.com/koxudaxi/datamodel-code-generator/security/advisories/GHSA-954p-556p-r752Vendor Advisories for CVE-2026-54690(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| datamodel-code-generator | 0.10.0 ... 0.9.4 (135 versions) | 0.61.0 | — |
Weakness Classification(1)
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.
- 2026-07-30 05:36 UTCEG score recompute
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 16:25 UTCEG score recompute
- 2026-07-29 15:33 UTCEG score recompute
- 2026-07-28 22:26 UTCEG score recompute
- 2026-07-28 21:54 UTCEG score recompute
- 2026-07-28 21:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-54690?
CVE-2026-54690 is a high vulnerability published on July 28, 2026. datamodel-code-generator generates Pydantic v2 models, dataclasses, TypedDict, and msgspec.Struct from OpenAPI, JSON Schema, GraphQL, Avro, Protobuf, and raw JSON, YAML, or CSV. From 0.9.1 until 0.61.0, datamodel-code-generator silently dereferences attacker-controlled JSON Schema $ref HTTP or…
When was CVE-2026-54690 disclosed?
CVE-2026-54690 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-54690 actively exploited?
CVE-2026-54690 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 88.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54690?
CVE-2026-54690 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-54690?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54690, 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-54690
Is Your Infrastructure Affected by CVE-2026-54690?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.