Datamodel Code Generator
Monthly
We need to produce a JSON object with the specified fields. We'll synthesize data from the input. CVE ID: CVE-2026-55389 Description: 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.62.0, datamodel-code-generator resolves JSON Schema $ref targets in src/datamodel_code_generator/parser/jsonschema.py through is_url and _get_ref_body without containing file:// or ../ traversal references to the input directory and without honoring --no-allow-remote-refs, allowing arbitrary local file reads. This issue is fixed in version 0.62.0. CVSS Score: 7.5 CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CWE: CWE-22 Tags: Path Traversal, Datamodel Code Generator CPE: cpe:2.3:a:koxudaxi:datamodel-code-generator:*:*:*:*:*:*:*:* Multi-source intelligence from GitHub Advisory: summary confirms arbitrary local file read via JSON-Schema $ref using file:// or ../ traversal, bypassing --no-allow-remote-refs. Details show code branches that handle local file reads without containment checks. Fixed in 0.62.0. POC? Not explicitly stated, but the issue is described with code fragments and test cases that demonstrate the vulnerability. No KEV mention. EPSS not provided. CWE-22 is path traversal. We need to analyze and fill all fields. product_name: "datamodel-code-generator" (the specific product name, 1-3 words) summary: Synthesize original summary, not copy description. Must start with impact verb and product. "Arbitrary local file read in datamodel-code-generator prior to 0.62.0 allows unauthenticated attackers to read any file on the system via crafted JSON Schema $ref references (file:// or ../ traversal), bypassing the --no-allow-remote-refs control. This is fixed in version 0.62.0. Exploit code exists (public test cases) but no active exploitation reported." Wait, "Arbitrary local file read" is the impact. So summary: "Arbitrary loc
Code injection in datamodel-code-generator 0.17.0–0.60.1 allows attackers who control a schema’s default_factory value to inject arbitrary Python expressions into generated models, achieving remote code execution when the target imports the poisoned module. The vulnerability affects all supported input types (JSON Schema, OpenAPI, YAML, JSON, Avro, Protobuf, XSD) and output model types (Pydantic v2, dataclass, msgspec). Public exploit code exists; the issue is fixed in version 0.60.2.
A DNS rebinding flaw in datamodel-code-generator's SSRF guard allows unauthenticated remote attackers to bypass the default `allow_private_network=False` restriction and reach internal services. The vulnerability affects versions prior to 0.63.0, where a time-of-check/time-of-use gap between URL validation and connection enables rebinding to private IPs. A public proof-of-concept exists, though no active exploitation in the wild is reported at this time.
Code injection via unescaped validator entries in datamodel-code-generator's --extra-template-data feature allows arbitrary Python code execution when a generated Pydantic v2 model is imported. Affects versions 0.52.1 through 0.60.1, with a fix in 0.60.2. Publicly available exploit code exists, though no active exploitation has been reported to CISA KEV.
We need to construct a JSON object that synthesizes data from multiple sources about CVE-2026-54690. The input includes description, CVSS, CWE, patch info, CPE, references, tags, etc. The output must be plain text strings, no arrays or objects, each field a coherent paragraph. Let's analyze the data. CVE ID: CVE-2026-54690 Description: datamodel-code-generator generates Pydantic v2 models, etc., from various schemas. From 0.9.1 until 0.61.0, datamodel-code-generator silently dereferences attacker-controlled JSON Schema $ref HTTP/HTTPS URLs via _get_ref_body, and --allow-remote-refs gate can warn instead of blocking, allowing SSRF. Fixed in 0.61.0. CVSS: 8.2 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N. So network, low complexity, no privileges, user interaction required, scope changed, high confidentiality, low integrity, no availability. CWE-918: Server-Side Request Forgery (SSRF). Tags: SSRF, Datamodel Code Generator. Patch: Available from vendor. Fix in version 0.61.0, commit. CPE: cpe:2.3:a:koxudaxi:datamodel-code-generator:*:*:*:*:*:*:*:* (asterisk, so all versions? Actually range is before fix, so vulnerable <=0.60.2? The description says from 0.9.1 until 0.61.0, with fix in 0.61.0, so vulnerable is >=0.9.1, <0.61.0. CPE * indicates all versions, but advisory says >=0.9.1. Probably better to specify version range. The EUVD affected versions: "datamodel-code-generator 0.9.1, < 0.61.0". References: GitHub advisory, commit, release tag. GHSA advisory from GitHub: summary says vulnerable to SSRF via JSON-Schema $ref to HTTP URL. It details that remote refs are fetched with no validation; --allow-remote-refs defaults to None which warns but then fetches; only explicit false blocks. Fetched body is parsed as sub-schema and reflected into generated code, leading to leakage. Only affects users who installed [http] extra. PoC available. Patch: commit adds --allow-private-network flag to block private network targets by default, and modifies behavi
Code injection via unsanitized schema extensions in datamodel-code-generator allows arbitrary Python code execution when the generated model is imported. Affects versions from 0.11.6 to 0.63.0. Public exploit code exists, but no active exploitation has been confirmed by CISA KEV.
Code injection in datamodel-code-generator versions before 0.60.1 allows an attacker who provides a malicious GraphQL schema to execute arbitrary Python code when a developer generates and imports the resulting model. The flaw exists because carriage return (\r) characters in Union type descriptions are not neutralized before being placed inside Python line comments, letting the rest of the description escape the comment and run as module‑level code upon import. A fix is available in version 0.60.1; no active exploitation is reported, and no public exploit is known.
Code injection in datamodel-code-generator allows an attacker who controls a JSON Schema to embed arbitrary Python code in generated model files, leading to arbitrary command execution when the module is imported. Affected versions 0.51.0 through 0.60.1 lack proper validation of the `x-python-type` extension, making the attack possible with default tool settings. No public exploit is identified at time of analysis, but the vulnerability is patched in version 0.60.2.
Sensitive header disclosure in datamodel-code-generator allows Authorization, Cookie, and Proxy-Authorization headers to be leaked to cross-origin redirect targets when fetching remote schemas. Affects versions prior to 0.63.0. A public proof-of-concept exploit exists, but no active exploitation has been reported and the CVSS score is low (3.7).
Arbitrary local file read in datamodel-code-generator versions 0.59.0 to 0.61.0 via path traversal in XSD parsing allows unauthenticated attackers who control an input XML Schema to read any file readable by the generator process, with the contents reflected into generated models. A public proof-of-concept exploit exists, and the issue is fixed in version 0.62.0.
We are generating a synthetic analysis for CVE-2026-54654. We have a lot of data: description, CVSS, CWE, tags, references, GHSA advisory with detailed description, PoC, patch commit details, CPE. Need to produce JSON fields as instructed. Fields: product_name, summary, technical_context, risk_assessment, affected_products, remediation, exploit_scenario, exploitation_conditions, attack_chain, confidence_notes, prevalence, prevalence_basis, assessed_cvss_vector, assessed_cvss_rationale, assessed_cvss40_vector. Let's extract key info: - Product: "datamodel-code-generator" (pip package, from koxudaxi). Product name should be 1-3 words: "datamodel-code-generator". - Description: Code injection via unescaped carriage return in `--extra-template-data` comment field, fixed in 0.60.2. - CVSS: 7.8, vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CWE-94: Code Injection. - Tags: Python, RCE, Code Injection, Datamodel Code Generator. - KEV: not mentioned, assume not in KEV. POC: mentioned in advisory (secret gist). But we can't confirm if it's public or private secret gist; the advisory says "Complete self contained POC is available at my secret gist", so the reporter likely privately shared with maintainers? Or the link is there? Since the GHSA description says "PoC available at my secret gist: https://...", but the URL is there. It's a public gist? Might be public. But we don't have explicit POC=YES flag. The tags don't say POC available. Advisory text includes PoC section but the URL is given. Could be public. We'll treat as "publicly available exploit code exists" since the gist URL is embedded in the advisory and likely accessible to anyone who reads it. However, we must be careful: the description says "Complete self contained POC is available at my secret gist" - "secret" might indicate private. But it's in a public security advisory, so it's exposed. It's not a standard public POC, but I'll note it as possible public POC. The instructions say: if POC=YES but no
Remote code execution in datamodel-code-generator prior to version 0.70.0 allows attackers who control input schemas to execute arbitrary Python code. By supplying a malicious customBasePath value containing embedded newlines and dot-free expressions, an attacker can inject code that executes when the generated module is imported. A patch is available in version 0.70.0; no public exploit is known at this time.
We need to produce a JSON object with the specified fields. We'll synthesize data from the input. CVE ID: CVE-2026-55389 Description: 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.62.0, datamodel-code-generator resolves JSON Schema $ref targets in src/datamodel_code_generator/parser/jsonschema.py through is_url and _get_ref_body without containing file:// or ../ traversal references to the input directory and without honoring --no-allow-remote-refs, allowing arbitrary local file reads. This issue is fixed in version 0.62.0. CVSS Score: 7.5 CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CWE: CWE-22 Tags: Path Traversal, Datamodel Code Generator CPE: cpe:2.3:a:koxudaxi:datamodel-code-generator:*:*:*:*:*:*:*:* Multi-source intelligence from GitHub Advisory: summary confirms arbitrary local file read via JSON-Schema $ref using file:// or ../ traversal, bypassing --no-allow-remote-refs. Details show code branches that handle local file reads without containment checks. Fixed in 0.62.0. POC? Not explicitly stated, but the issue is described with code fragments and test cases that demonstrate the vulnerability. No KEV mention. EPSS not provided. CWE-22 is path traversal. We need to analyze and fill all fields. product_name: "datamodel-code-generator" (the specific product name, 1-3 words) summary: Synthesize original summary, not copy description. Must start with impact verb and product. "Arbitrary local file read in datamodel-code-generator prior to 0.62.0 allows unauthenticated attackers to read any file on the system via crafted JSON Schema $ref references (file:// or ../ traversal), bypassing the --no-allow-remote-refs control. This is fixed in version 0.62.0. Exploit code exists (public test cases) but no active exploitation reported." Wait, "Arbitrary local file read" is the impact. So summary: "Arbitrary loc
Code injection in datamodel-code-generator 0.17.0–0.60.1 allows attackers who control a schema’s default_factory value to inject arbitrary Python expressions into generated models, achieving remote code execution when the target imports the poisoned module. The vulnerability affects all supported input types (JSON Schema, OpenAPI, YAML, JSON, Avro, Protobuf, XSD) and output model types (Pydantic v2, dataclass, msgspec). Public exploit code exists; the issue is fixed in version 0.60.2.
A DNS rebinding flaw in datamodel-code-generator's SSRF guard allows unauthenticated remote attackers to bypass the default `allow_private_network=False` restriction and reach internal services. The vulnerability affects versions prior to 0.63.0, where a time-of-check/time-of-use gap between URL validation and connection enables rebinding to private IPs. A public proof-of-concept exists, though no active exploitation in the wild is reported at this time.
Code injection via unescaped validator entries in datamodel-code-generator's --extra-template-data feature allows arbitrary Python code execution when a generated Pydantic v2 model is imported. Affects versions 0.52.1 through 0.60.1, with a fix in 0.60.2. Publicly available exploit code exists, though no active exploitation has been reported to CISA KEV.
We need to construct a JSON object that synthesizes data from multiple sources about CVE-2026-54690. The input includes description, CVSS, CWE, patch info, CPE, references, tags, etc. The output must be plain text strings, no arrays or objects, each field a coherent paragraph. Let's analyze the data. CVE ID: CVE-2026-54690 Description: datamodel-code-generator generates Pydantic v2 models, etc., from various schemas. From 0.9.1 until 0.61.0, datamodel-code-generator silently dereferences attacker-controlled JSON Schema $ref HTTP/HTTPS URLs via _get_ref_body, and --allow-remote-refs gate can warn instead of blocking, allowing SSRF. Fixed in 0.61.0. CVSS: 8.2 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N. So network, low complexity, no privileges, user interaction required, scope changed, high confidentiality, low integrity, no availability. CWE-918: Server-Side Request Forgery (SSRF). Tags: SSRF, Datamodel Code Generator. Patch: Available from vendor. Fix in version 0.61.0, commit. CPE: cpe:2.3:a:koxudaxi:datamodel-code-generator:*:*:*:*:*:*:*:* (asterisk, so all versions? Actually range is before fix, so vulnerable <=0.60.2? The description says from 0.9.1 until 0.61.0, with fix in 0.61.0, so vulnerable is >=0.9.1, <0.61.0. CPE * indicates all versions, but advisory says >=0.9.1. Probably better to specify version range. The EUVD affected versions: "datamodel-code-generator 0.9.1, < 0.61.0". References: GitHub advisory, commit, release tag. GHSA advisory from GitHub: summary says vulnerable to SSRF via JSON-Schema $ref to HTTP URL. It details that remote refs are fetched with no validation; --allow-remote-refs defaults to None which warns but then fetches; only explicit false blocks. Fetched body is parsed as sub-schema and reflected into generated code, leading to leakage. Only affects users who installed [http] extra. PoC available. Patch: commit adds --allow-private-network flag to block private network targets by default, and modifies behavi
Code injection via unsanitized schema extensions in datamodel-code-generator allows arbitrary Python code execution when the generated model is imported. Affects versions from 0.11.6 to 0.63.0. Public exploit code exists, but no active exploitation has been confirmed by CISA KEV.
Code injection in datamodel-code-generator versions before 0.60.1 allows an attacker who provides a malicious GraphQL schema to execute arbitrary Python code when a developer generates and imports the resulting model. The flaw exists because carriage return (\r) characters in Union type descriptions are not neutralized before being placed inside Python line comments, letting the rest of the description escape the comment and run as module‑level code upon import. A fix is available in version 0.60.1; no active exploitation is reported, and no public exploit is known.
Code injection in datamodel-code-generator allows an attacker who controls a JSON Schema to embed arbitrary Python code in generated model files, leading to arbitrary command execution when the module is imported. Affected versions 0.51.0 through 0.60.1 lack proper validation of the `x-python-type` extension, making the attack possible with default tool settings. No public exploit is identified at time of analysis, but the vulnerability is patched in version 0.60.2.
Sensitive header disclosure in datamodel-code-generator allows Authorization, Cookie, and Proxy-Authorization headers to be leaked to cross-origin redirect targets when fetching remote schemas. Affects versions prior to 0.63.0. A public proof-of-concept exploit exists, but no active exploitation has been reported and the CVSS score is low (3.7).
Arbitrary local file read in datamodel-code-generator versions 0.59.0 to 0.61.0 via path traversal in XSD parsing allows unauthenticated attackers who control an input XML Schema to read any file readable by the generator process, with the contents reflected into generated models. A public proof-of-concept exploit exists, and the issue is fixed in version 0.62.0.
We are generating a synthetic analysis for CVE-2026-54654. We have a lot of data: description, CVSS, CWE, tags, references, GHSA advisory with detailed description, PoC, patch commit details, CPE. Need to produce JSON fields as instructed. Fields: product_name, summary, technical_context, risk_assessment, affected_products, remediation, exploit_scenario, exploitation_conditions, attack_chain, confidence_notes, prevalence, prevalence_basis, assessed_cvss_vector, assessed_cvss_rationale, assessed_cvss40_vector. Let's extract key info: - Product: "datamodel-code-generator" (pip package, from koxudaxi). Product name should be 1-3 words: "datamodel-code-generator". - Description: Code injection via unescaped carriage return in `--extra-template-data` comment field, fixed in 0.60.2. - CVSS: 7.8, vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CWE-94: Code Injection. - Tags: Python, RCE, Code Injection, Datamodel Code Generator. - KEV: not mentioned, assume not in KEV. POC: mentioned in advisory (secret gist). But we can't confirm if it's public or private secret gist; the advisory says "Complete self contained POC is available at my secret gist", so the reporter likely privately shared with maintainers? Or the link is there? Since the GHSA description says "PoC available at my secret gist: https://...", but the URL is there. It's a public gist? Might be public. But we don't have explicit POC=YES flag. The tags don't say POC available. Advisory text includes PoC section but the URL is given. Could be public. We'll treat as "publicly available exploit code exists" since the gist URL is embedded in the advisory and likely accessible to anyone who reads it. However, we must be careful: the description says "Complete self contained POC is available at my secret gist" - "secret" might indicate private. But it's in a public security advisory, so it's exposed. It's not a standard public POC, but I'll note it as possible public POC. The instructions say: if POC=YES but no
Remote code execution in datamodel-code-generator prior to version 0.70.0 allows attackers who control input schemas to execute arbitrary Python code. By supplying a malicious customBasePath value containing embedded newlines and dot-free expressions, an attacker can inject code that executes when the generated module is imported. A patch is available in version 0.70.0; no public exploit is known at this time.