Loading story…
A high-severity code injection vulnerability, CVE-2026-54653, affects datamodel-code-generator versions 0.17.0 through 0.60.1, allowing attacker-controlled JSON Schema input to inject unsafe default_factory values into generated Python models. When a victim later imports the generated code, the embedded Python expression can execute, creating a remotely exploitable path from untrusted schema parsing to code execution. The issue is tracked with CVSS 8.8 and mapped to CWE-94 and CWE-1336.
Project maintainers addressed the flaw in version 0.60.2, which includes fixes for this and other code-injection vectors involving schema-provided default_factory, x-python-type, comment data passed through --extra-template-data, and Pydantic v2 validator definitions supplied via --validators or --extra-template-data. The patch for default_factory now limits accepted values to an allowlist of dict, list, and set, rejecting code-like strings, lambdas, function references, and None; defenders are advised to upgrade to 0.60.2, review previously generated models for unsafe default_factory usage, and avoid importing generated code produced from untrusted schemas until updated.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Version 0.60.2 of datamodel-code-generator was released to address multiple security issues, including code injection via attacker-controlled default_factory values. The release also fixed related injection vectors involving x-python-type, comment entries from extra template data, and Pydantic v2 validator definitions.
A source code patch was committed to datamodel-code-generator to restrict schema-supplied default_factory values to an allowlist of "dict", "list", and "set", rejecting other values as unsafe. The change also added tests covering code-like strings, lambdas, function references, and None.
CVE-2026-54653 was publicly documented as a high-severity code injection vulnerability affecting datamodel-code-generator versions 0.17.0 through 0.60.1. The issue stems from preserving attacker-controlled default_factory values during JSON Schema parsing and was noted as fixed in version 0.60.2.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcecvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A high-severity server-side request forgery vulnerability, **CVE-2026-54691**, was disclosed in `datamodel-code-generator`, affecting versions `0.9.1` through `0.60.x`. The flaw stems from the tool's HTTP fetch logic accepting user-supplied `--url` targets and redirect destinations without validating the host or IP address, allowing requests to reach **localhost**, loopback, private, link-local, metadata, and other non-public network resources. The issue is rated **CVSS 8.2** and is considered remotely exploitable. The project addressed the issue in version `0.61.0` with changes that block HTTP(S) requests to non-public network targets by default and validate redirect destinations before following them. The patch also introduced `--allow-private-network` and `--no-allow-private-network` options so users can explicitly opt in to trusted internal schema endpoints, while preserving public remote schema and `$ref` fetching behavior with warnings and updated tests, documentation, and CLI/config handling.
Jul 29, 2026
A high-severity server-side request forgery flaw tracked as **CVE-2026-54690** affects `datamodel-code-generator` when it processes attacker-controlled JSON Schema `$ref` values pointing to `http` or `https` URLs. In vulnerable releases, the tool silently resolves remote references during schema processing, allowing outbound requests to arbitrary destinations; one report places the affected range at **0.9.1 through 0.60.x**, while another indicates exposure through **0.61.0**. The issue has a **CVSS v3.1 score of 8.2** and is tied to schema resolution and HTTP fetch logic in files including `jsonschema.py` and `http.py`. Researchers said the vulnerable code passes untrusted URLs directly to the HTTP client, follows redirects, and does not adequately restrict hostnames, ports, or IP ranges, creating a path to reach internal services such as `127.0.0.1` and cloud metadata endpoints like `169.254.169.254`. Fetched content may also be incorporated into generated output, raising information disclosure risk in addition to SSRF. The issue is fixed in **version 0.61.0**, with the patch adding URL validation and blocking localhost-style and non-global IP targets unless private-network access is explicitly enabled; recommended mitigations include disabling remote reference resolution or blocking private-network access.
Jul 29, 2026
A critical software supply-chain vulnerability, **CVE-2026-23947** (CVSS **9.3**), was disclosed in *Orval*, a widely used npm tool that generates type-safe TypeScript/JavaScript clients from OpenAPI/Swagger specifications. The flaw allows **code injection** when Orval processes untrusted or compromised API specifications: attacker-controlled content in the `x-enumDescriptions` / `x-enum-descriptions` field is embedded without proper escaping in `getEnumImplementation()`, enabling malicious TypeScript/JavaScript to be written into generated client/schema files during `const enum` generation. Successful exploitation can lead to **arbitrary code execution in environments consuming the generated clients**, shifting risk to downstream developers and build/runtime pipelines that treat generated code as trusted. Affected versions are reported as **7.10.0 through 8.0.2**, and vendor guidance indicates updating to a fixed release (noted as *Orval* **8.0.2**) to remediate; the issue is described as similar to **CVE-2026-22785** but impacting a different `@orval/core` code path not covered by the earlier fix.
Jun 29, 2026