CVE-2026-108384: dataclasses-avroschema allows code injection through fixed-type aliases supplied as a bare string

Published Oct 13, 2026
·
Updated

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.parsefixed interpolates a fixed type's aliases value directly into a generated types.confixed annotation. A list is represented with quoted entries, but a bare string is emitted as an unquoted Python expression and evaluated when the generated module is imported, allowing arbitrary code execution from a crafted schema. Version 0.70.6 fixes the vulnerability by rejecting aliases values that are not lists.

Affected Software

1 affected component
pypi/dataclasses-avroschema>=0.38.0<=0.70.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade dataclasses-avroschema to a version that resolves this vulnerability.

    Fixed in 0.70.6

Event History

Oct 13, 2026
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using dataclasses-avroschema versions 0.38.0 through 0.70.5 are exposed when they generate Python code from Avro schemas containing fixed types. The issue is triggered when the generated module is imported.

2

What does an attacker need to exploit it?

An attacker needs to supply or influence an Avro schema with a fixed type whose aliases field is a bare string rather than a list. User interaction is required according to the provided vector, and the crafted schema must be processed into generated Python code and imported.

3

Are normal list-form aliases affected?

The described unsafe behavior applies to aliases supplied as a bare string. List-form aliases are emitted with quoted entries and are not described as vulnerable.

4

What should be done if upgrading is not immediately possible?

Do not generate and import Python modules from untrusted Avro schemas, and reject fixed-type aliases values unless they are lists. This mirrors the validation introduced in version 0.70.6.

5

How can I determine whether my environment is affected?

Check whether dataclasses-avroschema is installed at a version from 0.38.0 through 0.70.5 and whether your workflow generates Python code from Avro schemas. Review schemas accepted by that workflow for fixed-type aliases represented as bare strings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203