CVE-2026-108384

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

GHSA-8j5c-xq6f-2c43 ↗EUVD-2026-98981 ↗

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.
marcosschroh dataclasses-avroschema <= 0.70.5
fixed in >= 0.70.6
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-1543Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/dataclasses-avroschema
6d 23h 01msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+12h50m
0
+2h
+4h
+6h
+8h
+10h

description

dataclasses-avroschema versions 0.38.0 through 0.70.5 can embed an unsafe fixed-type alias value in generated Python code. An attacker who can supply a crafted Avro schema may cause code to run when the resulting module is imported.

mitigation

Upgrade dataclasses-avroschema to version 0.70.6 or later. Until upgrading, do not generate or import code from untrusted Avro schemas.

fixed in >= 0.70.6

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.
0.34%26th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 17:53Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-13 17:53Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1543",
  "cve_id": "CVE-2026-108384",
  "display_id": "CVE-2026-108384",
  "ghsa_id": "GHSA-8j5c-xq6f-2c43",
  "euvd_id": "EUVD-2026-98981",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Code injection in dataclasses-avroschema code generation",
  "summary": "dataclasses-avroschema versions 0.38.0 through 0.70.5 can embed an unsafe fixed-type alias value in generated Python code. An attacker who can supply a crafted Avro schema may cause code to run when the resulting module is imported.",
  "mitigation": "Upgrade dataclasses-avroschema to version 0.70.6 or later. Until upgrading, do not generate or import code from untrusted Avro schemas.",
  "vendor": "marcosschroh",
  "product": "dataclasses-avroschema",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 0.70.5"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        ">= 0.70.6"
      ],
      "package_name": "dataclasses-avroschema",
      "purl": "pkg:pypi/dataclasses-avroschema"
    }
  ],
  "cwes": [
    94
  ],
  "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": 0.0034,
  "epss_percentile": 0.2635,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.68800075,
  "t0_at": "2026-10-13T17:53:48.228000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T17:53:48.228000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T17:53:48.228000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108384"
    }
  }
}

published 2026-10-14 06:30Z
last change 2026-10-21 05:31Z

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.