Advisory

GHSA-q4c3-7575-55j2

Also known as: BIT-airflow-2026-67260, CVE-2026-67260, PYSEC-2026-3707

Summary

Apache Airflow scheduler unsafely deserializes human-in-the-loop task next_kwargs

Details

Apache Airflow 3.3.0 moved human-in-the-loop tasks from the triggerer to a new awaiting_input task state swept by the scheduler. That sweep deserializes the task instance's next_kwargs without an allow-list, so a Dag author — who controls that value through the task execution API — can cause an arbitrary module import and object instantiation inside the scheduler process, or terminate the scheduler job. No non-default configuration is required: the sweep runs unconditionally every 15 seconds, and the default allowed_deserialization_classes setting does not cover this code path. Versions before 3.3.0 are not affected, because human-in-the-loop tasks deferred onto the triggerer instead. This is a different code path from CVE-2026-58076, which covers the same unguarded exception-node deserialization reached elsewhere — deployments that applied that fix must upgrade for this issue as well. Users are advised to upgrade to apache-airflow 3.3.1 or later.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-08-12 18:31 UTC
Modified
2026-10-02 23:41 UTC

Affected packages and fixes

apache-airflow

PyPI · All systems

Affected

  • introduced 3.3.0, fixed 3.3.1 (ecosystem)

Fixed versions

3.3.1

Fix

  • Fixed version 3.3.1
    pip install --upgrade apache-airflow==3.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences