CVE-2026-127208

waiting for further signalsZero needs more public information before it can validate it.

GHSA-5hqf-87jh-5c5q ↗EUVD-2026-124714 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
datamodel-code-generator < 0.84.0
fixed in 0.84.0
ETK-2026-4325Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 46msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h05m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

datamodel-code-generator before 0.84.0 can emit generated model code that leads to arbitrary code execution. An attacker must be able to supply a malicious JSON Schema that is processed and whose generated models are later imported or rebuilt.

mitigation

Upgrade datamodel-code-generator to version 0.84.0 or later. Until upgraded, do not process untrusted JSON Schema inputs or import generated models from them.

fixed in 0.84.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 20:58Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-12 20:58Z
    ghsa: trigger signal, started the run
  2. 2026-11-12 20:58Z

this entry in the feed

GET /api/v1/feed/CVE-2026-127208

{
  "etk_id": "ETK-2026-4325",
  "cve_id": "CVE-2026-127208",
  "display_id": "CVE-2026-127208",
  "ghsa_id": "GHSA-5hqf-87jh-5c5q",
  "euvd_id": "EUVD-2026-124714",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Code injection in datamodel-code-generator",
  "summary": "datamodel-code-generator before 0.84.0 can emit generated model code that leads to arbitrary code execution. An attacker must be able to supply a malicious JSON Schema that is processed and whose generated models are later imported or rebuilt.",
  "mitigation": "Upgrade datamodel-code-generator to version 0.84.0 or later. Until upgraded, do not process untrusted JSON Schema inputs or import generated models from them.",
  "vendor": "datamodel-code-generator",
  "product": "datamodel-code-generator",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.84.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.84.0"
      ],
      "package_name": "datamodel-code-generator",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.018538266666667,
  "t0_at": "2026-11-12T20:58:59.634000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T20:58:59.634000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T20:58:59.634000+00:00",
      "url": "https://github.com/advisories/GHSA-5hqf-87jh-5c5q"
    }
  }
}

published 2026-11-12 21:56Z
last change 2026-11-12 22:58Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.