dataclasses-avroschema generates Avro schemas from Python dataclasses, Pydantic models, and Faust Records and generates Python code from Avro schemas. From version 0.38.0 through 0.70.5, BaseGenerator.parse_fixed inserts a fixed type's namespace value between quotes inside a generated types.confixed annotation without escaping or validating it. A crafted quote can terminate the namespace string and alter the surrounding annotation expression, which Python evaluates when the generated class is defined, allowing arbitrary code execution. Version 0.70.6 fixes the vulnerability by requiring the namespace to be a dot-separated sequence of valid Avro names.
CVE-2026-108379
HIGHPre-NVD 8.88.8
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHlow confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%The EG Score, 8.8 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 13, 2026
Last Modified
October 13, 2026
Advisory Details (3)
Auto-updated Oct 13, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available
0.70.6
Patch available: marcosschroh/dataclasses-avroschema 0.70.6
https://github.com/marcosschroh/dataclasses-avroschema/releases/tag/0.70.6GitHub commit Patch Available
commit 429f3d705d2d (marcosschroh/dataclasses-avroschema)
Patch available: marcosschroh/dataclasses-avroschema 0.70.6 (contains commit 429f3d705d2d)
https://github.com/marcosschroh/dataclasses-avroschema/commit/429f3d705d2d04c0c65e2ef832daed5ff91318fcGitHub advisoryMentions a patch (unverified)🟡 PoC Available
Code injection through a `fixed` type's namespace rendered into the generated type annotation · Advisory · marcosschroh/dataclasses-avroschema · GitHub
https://github.com/marcosschroh/dataclasses-avroschema/security/advisories/GHSA-h9q3-f96w-f88jWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 21:27 UTCEG score recompute
- 2026-10-13 20:27 UTCEG score recompute
- 2026-10-13 18:26 UTCEG score recompute
- 2026-10-13 17:52 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-10-13 17:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-108379?
CVE-2026-108379 is a high-severity vulnerability; its CVE record was published on October 13, 2026. dataclasses-avroschema generates Avro schemas from Python dataclasses, Pydantic models, and Faust Records and generates Python code from Avro schemas. From version 0.38.0 through 0.70.5, BaseGenerator.parse_fixed inserts a fixed type's namespace value between quotes inside a generated…
When was the CVE record for CVE-2026-108379 published?
The CVE record for CVE-2026-108379 was published on October 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-108379?
CVE-2026-108379 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-108379?
A fix for CVE-2026-108379 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108379
Is Your Infrastructure Affected by CVE-2026-108379?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.