CVE-2026-55391

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.2%, top 85% 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
Elevated
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 Pydantic v2 models, dataclasses, TypedDict, and msgspec.Struct from OpenAPI, JSON Schema, GraphQL, Avro, Protobuf, and raw JSON, YAML, or CSV. Prior to 0.63.0, datamodel-code-generator validates a URL host once in src/datamodel_code_generator/http.py through get_body, _validate_url_for_fetch, and _get_ips_from_host, but then lets httpx resolve the host again for the connection, allowing DNS rebinding to bypass allow_private_network=False and reach internal services. This issue is fixed in version 0.63.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 28, 2026

Last Modified

August 6, 2026

Advisory Details (3)

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

0.63.0

Patch available: koxudaxi/datamodel-code-generator 0.63.0

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

commit 25c8b7e49741 (koxudaxi/datamodel-code-generator)

Patch available: koxudaxi/datamodel-code-generator 0.63.0 (contains commit 25c8b7e49741)

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

SSRF protection bypass via DNS rebinding · Advisory · koxudaxi/datamodel-code-generator · GitHub

https://github.com/koxudaxi/datamodel-code-generator/security/advisories/GHSA-vx7x-vcc2-c44g

Vendor Advisories for CVE-2026-55391(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.0.1 ... 0.9.4 (253 versions)0.63.0

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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-09-15 08:32 UTCEG score recompute
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-13 20:35 UTCEG score recompute
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 18:14 UTCEG score recompute
  6. 2026-09-11 15:21 UTCEG score recompute
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 20:47 UTCEG score recompute
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-09 07:58 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 20:54 UTCEG score recompute
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 22:47 UTCEG score recompute
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 19:08 UTCEG score recompute
  17. 2026-09-05 05:24 UTCEG score recompute
  18. 2026-09-04 11:59 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 22:50 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-31 01:55 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 60 more
  1. 2026-08-30 12:44 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 23:28 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 20:56 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 15:29 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 02:12 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 23:51 UTCEG score recompute
  12. 2026-08-24 10:41 UTCEG score recompute
  13. 2026-08-22 05:59 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 03:37 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 00:55 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 22:19 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-16 17:05 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 03:54 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:33 UTCEG score recompute
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-13 23:12 UTCEG score recompute
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 20:51 UTCEG score recompute
  30. 2026-08-12 13:51 UTCEPSS rescore
  31. 2026-08-11 18:31 UTCEG score recompute
  32. 2026-08-11 05:19 UTCEG score recompute
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-09 13:48 UTCEG score recompute
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 00:38 UTCEG score recompute
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-07 22:17 UTCEG score recompute
  39. 2026-08-06 19:55 UTCEG score recompute
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-05 20:28 UTCEG score recompute
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-04 18:05 UTCEG score recompute
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:39 UTCEPSS rescore
  46. 2026-08-03 15:24 UTCEG score recompute
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 13:03 UTCEG score recompute
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 10:42 UTCEG score recompute
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 16:58 UTCEG score recompute
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 03:30 UTCEG score recompute
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-29 14:20 UTCEG score recompute
  57. 2026-07-29 13:59 UTCEG score recompute
  58. 2026-07-28 22:26 UTCEG score recompute
  59. 2026-07-28 21:55 UTCEG score recompute
  60. 2026-07-28 21:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55391?
CVE-2026-55391 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. Prior to 0.63.0, datamodel-code-generator validates a URL host once in src/datamodelcodegenerator/http.py through…
When was CVE-2026-55391 disclosed?
CVE-2026-55391 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55391 actively exploited?
CVE-2026-55391 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 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-55391?
CVE-2026-55391 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55391?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55391, 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-55391

Explore →

Is Your Infrastructure Affected by CVE-2026-55391?

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