Security readout for executives and security teams
Plain-English summary
A malicious JSON Schema can abuse the x-python-type extension so generated Python code runs attacker-controlled instructions when imported. This could compromise the importing user or system, exposing data, altering files, or disrupting services. The risk is concentrated in workflows that accept schemas from untrusted or insufficiently controlled sources.
Executive priority
Prioritize remediation for CI, build, developer, or service workflows that process third-party schemas and import generated modules. Upgrade promptly and review previously generated artifacts. Lower priority may be reasonable only after confirming schemas are trusted, affected versions are absent, or generated output is never imported.
Technical view
Versions 0.51.0 through 0.60.1 insufficiently validate x-python-type values in the JSON Schema parser. Attacker-controlled values can enter generated field annotations and execute as Python when the generated module is imported. This is CWE-94 code injection with CVSS 3.1 score 7.8. Version 0.60.2 contains the fix.
Likely exposure
Exposure requires an affected generator version, attacker-influenced JSON Schema content using x-python-type, and subsequent import of the generated Python module. CI pipelines, developer tooling, and automated schema-processing services are higher concern when schema provenance is not strictly controlled. Systems that never process untrusted schemas or import generated output have reduced exposure.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires user or automated workflow interaction because malicious schema content must be processed and the resulting module imported. Successful exploitation could affect confidentiality, integrity, and availability within the importing process's privileges.
Researcher notes
The vulnerable path is _get_python_type_override in the JSON Schema parser. The security boundary failure is insufficient validation before x-python-type content reaches Python annotations. Import is the execution trigger described by the advisory. The source bundle provides no evidence of exploitation in the wild, public weaponization, or affected products beyond datamodel-code-generator.
Mitigation direction
- Upgrade datamodel-code-generator to version 0.60.2 or later.
- Regenerate affected models from trusted schemas after upgrading.
- Reject or quarantine schemas from untrusted or unverifiable sources.
- Avoid importing output generated by vulnerable versions until reviewed.
- Check the vendor advisory for any subsequent remediation guidance.
Validation and detection
- Inventory installed, locked, and build-time datamodel-code-generator versions.
- Identify workflows accepting externally supplied or repository-contributed JSON Schemas.
- Determine whether generated modules are automatically imported or executed.
- Verify production and CI environments use version 0.60.2 or later.
- Review previously generated modules and their source-schema provenance.
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-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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-54655 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
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/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:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/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-m34r-v34r-rf9qCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/koxudaxi/datamodel-code-generator/commit/2c93c9b712f43391dcfa975a1e4aa0b7c93ccbbaCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/koxudaxi/datamodel-code-generator/releases/tag/0.60.2CVE reference, GitHub_M · x_refsource_MISC
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 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.