← Back
CVE-2026-54690
high
CVSS 8.2
SSRF (Server-Side Request Forgery) in datamodel-code-generator (CVE-2026-54690)
Summary
SSRF in datamodel-code-generator (CVE-2026-54690). Confidential information can be exposed externally. Exploitable via ``None``. Mitigation: upgrade to `0.61.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54690** has been found in datamodel-code-generator.
Attackers can target a specific entry point like ``None`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade datamodel-code-generator to **0.61.0** or later.
If unsure, ask your IT team or search "datamodel-code-generator CVE-2026-54690" on the vendor's site.
CVE-2026-54690 (datamodel-code-generator) — CWE-918 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `None` / `_get_ref_body` / `a321547e` / `allow_remote_refs`
Patched: `0.61.0` — 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
**SSRF** (CWE-918) exists in datamodel-code-generator. Attackers reach the vulnerable code path via ``None`` without authentication.
📍 Affected scope
datamodel-code-generator — . Attack surface: `None` / `_get_ref_body` / `a321547e` / `allow_remote_refs`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.61.0**.
🛡️ 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.61.0ステージング環境で 0.61.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.61.0"}]}]