Security readout for executives and security teams
Plain-English summary
A crafted schema can cause this code-generation tool to place an attacker-controlled Python expression into generated models. When a developer, build system, or application imports that generated code, the expression may run with that process’s permissions, potentially compromising data, code, and service availability.
Executive priority
Prioritize immediate remediation for internet-facing schema services and automated build pipelines that consume external specifications. Other installations should patch promptly after determining whether untrusted schemas can enter generation workflows. Investigate suspicious generated files and related process activity if exposure existed.
Technical view
Versions 0.17.0 through 0.60.1 preserve untrusted default_factory values while parsing schemas and emit them into Pydantic or dataclass field declarations. Importing the generated Python module can evaluate the injected expression. CVE-2026-54653 is rated CVSS 8.8 and maps to code-injection weaknesses CWE-1336 and CWE-94. Version 0.60.2 fixes the issue.
Likely exposure
Exposure is highest where affected versions generate Python models from external, user-supplied, downloaded, or otherwise untrusted schemas, and those models are subsequently imported. Installations processing only controlled schemas have lower likelihood, but compromised dependencies or schema repositories remain relevant. Mere installation is insufficient; the vulnerable generation-to-import workflow must occur.
Exploitation context
A public exploit reference exists, demonstrating that technical details are available. However, the supplied sources do not establish active exploitation, and the CVE is not listed as KEV. Exploitation requires a victim workflow to process attacker-controlled schema content and later import the generated Python model.
Researcher notes
The vulnerable flow is JsonSchemaObject initialization through field extras into emitted Field(default_factory=...) or field(default_factory=...). Execution occurs when generated code is imported, explaining the user-interaction requirement. The supplied evidence supports affected versions from 0.17.0 inclusive to below 0.60.2; it does not document confirmed attacks.
Mitigation direction
- Upgrade datamodel-code-generator to version 0.60.2 or later.
- Stop processing untrusted schemas with affected versions until upgraded.
- Quarantine generated models derived from external or unverified schemas.
- Regenerate affected models from trusted inputs after upgrading.
- Apply least privilege to build, generation, and application processes.
Validation and detection
- Inventory datamodel-code-generator versions across developer systems, CI pipelines, and build images.
- Identify workflows that accept schemas from users, partners, repositories, or network sources.
- Trace whether generated Python modules are automatically imported, tested, packaged, or deployed.
- Review generated models for unexpected default_factory expressions or unexplained changes.
- Confirm upgraded pipelines reject or safely handle malicious default_factory content.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1336: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-54653 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/koxudaxi/datamodel-code-generator/security/advisories/GHSA-386q-5hp3-95m9CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/koxudaxi/datamodel-code-generator/commit/17fc235e234cbcfaaadef8c74cb72c9687db0d1dCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/koxudaxi/datamodel-code-generator/releases/tag/0.60.2CVE reference, GitHub_M · x_refsource_MISC
- https://gist.github.com/thegr1ffyn/9648b0fe4fcf7d569ac8e61dd11eebafCVE reference, CISA-ADP · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements Used in a Template Engine
Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.