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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/70685 Issue Tracking, Patch
- https://lists.apache.org/thread/vygr0fh82cjzjp5k4vtfmboxryvm3lyn Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.3 · apacheNVD modified 2026-10-23 20:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*
References 3
- https://github.com/apache/airflow/pull/70685 Issue Tracking, Patch
- https://lists.apache.org/thread/vygr0fh82cjzjp5k4vtfmboxryvm3lyn Mailing List, Vendor Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-58076 Not Applicable