PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-55390 koxudaxi CVE debrief

CVE-2026-55390 is a vulnerability in the datamodel-code-generator tool that allows arbitrary local files to be read and reflected into generated models. The issue is fixed in version 0.62.0. This vulnerability impacts defenders responsible for maintaining and securing systems that use datamodel-code-generator, as it could lead to potential unauthorized local file reading and reflection into generated models. Defenders should assess their exposure and take necessary actions to mitigate the vulnerability.

Vendor
koxudaxi
Product
datamodel-code-generator
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-28
Original CVE updated
2026-10-23
Advisory published
2026-07-28
Advisory updated
2026-10-23

Who should care

Defenders responsible for maintaining and securing systems that use datamodel-code-generator should assess their exposure and take necessary actions to mitigate the vulnerability. This includes verifying if they are using a vulnerable version, reviewing generated models for potential security issues, and upgrading to version 0.62.0 or later.

Why it matters

CVE-2026-55390 is a vulnerability in datamodel-code-generator that allows arbitrary local file reading and reflection into generated models. Defenders should verify their exposure, assess potential security issues, and upgrade to version 0.62.0 or later.

  • Potential unauthorized local file reading
  • Potential security issues in generated models
  • Need to verify and upgrade to a secure version

Technical summary

The datamodel-code-generator tool generates Python data models from schema definitions. From version 0.59.0 to 0.62.0, the tool is vulnerable to arbitrary local file reading and reflection into generated models due to improper handling of XML Schema parsing. This issue allows defenders to verify their exposure, assess potential security issues, and upgrade to a secure version. The vulnerability is fixed in version 0.62.0, and defenders should prioritize verifying if they are using a vulnerable version and upgrading.

Defensive priority

Defenders should prioritize verifying if they are using a vulnerable version of datamodel-code-generator and upgrading to version 0.62.0 or later.

Recommended defensive actions

  • Verify if you are using a vulnerable version of datamodel-code-generator
  • Upgrade to version 0.62.0 or later
  • Review generated models for potential security issues
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide information about the vulnerability, but details about exploitation or victim impact are not available. The vulnerability allows arbitrary local file reading and reflection into generated models due to improper handling of XML Schema parsing in the datamodel-code-generator tool. Defenders should verify their exposure, assess potential security issues, and upgrade to version 0.62.0 or later.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-55390 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-55390

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-55390 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-55390

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.