CVE-2026-108385: high-severity vulnerability in marcosschroh dataclasses-avroschema
dataclasses-avroschema enum symbols can inject statements through generated member names
Published
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.8epss 0.4%
exploitation probability
0.4%top 70% of all CVEs
observed exploitation
nono source reports it
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_enum and EnumRepresentation.render_symbols use each schema-controlled enum symbol as a generated enum member name after case conversion but without validating it as an identifier. When generator classes are used directly, newlines and punctuation can inject constrained statements into the generated enum class body, allowing namespace modification or preventing the module from loading. Version 0.70.6 fixes the vulnerability by validating every enum symbol as a name.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
marcosschroh · dataclasses-avroschemaRelated CVEs — marcosschroh dataclasses-avroschema
In the same product, most dangerous first.
CVE-2026-108376HIGHdataclasses-avroschema allows code injection through record names in generated default factoriesEPSS 0.5%CVE-2026-108375HIGHdataclasses-avroschema allows code injection through generated field-default literalsEPSS 0.5%CVE-2026-108380HIGHdataclasses-avroschema field documentation allows code injection in generated Pydantic descriptionsEPSS 0.4%CVE-2026-108381HIGHdataclasses-avroschema pydantic-class metadata allows code injection in generated annotationsEPSS 0.4%CVE-2026-108377HIGHdataclasses-avroschema allows code injection through generated Meta.schema_nameEPSS 0.4%CVE-2026-108382HIGHdataclasses-avroschema allows code injection through generated enum-symbol string literalsEPSS 0.4%