datamodel-code-generator vulnerable to code injection via unescaped carriage return in --extra-template-data comment field

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.8 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-54654: 0.21% estimated exploitation activity in the next 30 days; percentile 11.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary datamodel-code-generator is vulnerable to code injection when a developer passes an --extra-template-data file whose comment value contains a literal \r (carriage return). The comment variable is rendered into a Python

comment in six built-in templates with no line-terminator escaping. Python's tokenizer treats a bare CR as a physical-line terminator (see Python language reference — Physical lines), so the comment ends at the \r and the text after it is parsed as Python, including, when the CR is followed by suitable indentation, as a statement within the class body that follows on the next template line. Details The vulnerable templates each contain

{{ comment }} with no escaping: - src/datamodelcodegenerator/model/template/TypeAliasAnnotation.jinja2:12 and :19 - src/datamodelcodegenerator/model/template/TypeAliasType.jinja2:12 and :19 - src/datamodelcodegenerator/model/template/TypeStatement.jinja2:12 and :19 -…

Published by the source

28 Jul 2026, 21:50 UTC

Last modified by the source

28 Jul 2026, 21:50 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wjv6-jcfj-mf9r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54654

Advisory: `datamodel-code-generator` vulnerable to code injection via unescaped carriage return in `--extra-template-data` `comment` field
IDs: CVE-2026-54654, GHSA-wjv6-jcfj-mf9r
Record: https://patchnext.com/advisories/cve-2026-54654 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: datamodel-code-generator 0.60.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI datamodel-code-generator: affected >= 0.14.1, <= 0.60.1; fixed in 0.60.2

## Suggested inspection (read-only)
- `python -m pip show datamodel-code-generator`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on datamodel-code-generator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wjv6-jcfj-mf9r (GitHub-reviewed advisory GHSA-wjv6-jcfj-mf9r lists affected ranges: PyPI datamodel-code-generator >=0.14.1 <=0.60.1)

Commands are suggestions: review each one before running it.