CVE-2026-67260

published 12 Aug 2026 · updated 3 Nov 2026

Apache Airflow: DAG-author remote code execution on the Scheduler via awaiting_input next_kwargs deserialization

7.3HighCVSS 7.3EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Airflow 3.3.1 and 3.3.1.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ApacheAirflow>=3.3.0 <3.3.13.3.1
Apache Software Foundation>=3.3.0 <3.3.13.3.1

Coverage

News and research mentioning this CVE

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Airflow, strongest first

10.0CriticalCISA KEVPublic exploit

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67260 severity on Zeptric[![CVE-2026-67260](https://zeptric.io/badge/cve/CVE-2026-67260.svg)](https://zeptric.io/cve/CVE-2026-67260)