← Back
CVE-2026-54653
high
CVSS 8.8
Code Injection in datamodel-code-generator (CVE-2026-54653)
Summary
code injection in datamodel-code-generator (CVE-2026-54653). Successful exploitation can lead to full system takeover. Exploitable via ``import``. Mitigation: upgrade to `0.60.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54653** has been found in datamodel-code-generator.
Attackers can target a specific entry point like ``import`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade datamodel-code-generator to **0.60.2** or later.
If unsure, ask your IT team or search "datamodel-code-generator CVE-2026-54653" on the vendor's site.
CVE-2026-54653 (datamodel-code-generator) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `import` / `extras` / `DEFAULT_FIELD_KEYS` / `JsonSchemaObject.__init__`
Patched: `0.60.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in datamodel-code-generator. Attackers reach the vulnerable code path via ``import`` without authentication.
📍 Affected scope
datamodel-code-generator — . Attack surface: `import` / `extras` / `DEFAULT_FIELD_KEYS` / `JsonSchemaObject.__init__`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.60.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'datamodel-code-generator' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'datamodel-code-generator' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `datamodel-code-generator` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade datamodel-code-generator to 0.60.2ステージング環境で 0.60.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
datamodel-code-generator
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.60.2"}]}]
References
- advisory 134c704f-9b21-4f2e-91b3-4a467353bcc0
- exploit [email protected]
- patch [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-386q-5hp3-95m9