CVE-2026-67260: Apache Airflow unsafe deserialization in awaiting_input task state

CVE-2026-67260 · Severity: high · CVSS 7.3 · Published 2026-08-12

Apache Airflow 3.3.0 introduced a new human-in-the-loop task scheduling mechanism that processes task metadata on the scheduler every 15 seconds. A DAG author can exploit unsafe deserialization of task parameters to execute arbitrary code or crash the scheduler, compromising the integrity and availability of the entire Airflow workflow system.

Technologies: Apache Airflow, apache-airflow (PyPI). Vendors: Apache, PyPI.

Quick answers

Is CVE-2026-67260 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67260 being exploited in the wild.
How severe is CVE-2026-67260?
High severity, with a CVSS score of 7.3, published 12 August 2026.
Which products and versions are affected?
Apache Airflow 3.3.0; apache-airflow (PyPI) >= 3.3.0, < 3.3.1, ECOSYSTEM:introduced=3.3.0,fixed=3.3.1.
Is there a fix for CVE-2026-67260?
Yes. apache-airflow (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67260 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67260?
Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • apache-airflow (PyPI): upgrade to 3.3.1 or later
    pip install "apache-airflow>=3.3.1"

Technical details

This vulnerability is an unsafe deserialization flaw (CWE-502) in Apache Airflow 3.3.0's new `awaiting_input` task state handler. The scheduler's periodic sweep (every 15 seconds by default) deserializes a task instance's `next_kwargs` field without validating against an allow-list. A DAG author who controls task execution API inputs can inject malicious serialized objects that trigger arbitrary module imports and object instantiation within the scheduler process, or cause denial of service via unhandled exceptions. The vulnerability affects all Airflow 3.3.0 deployments by default, as the unsafe code path runs unconditionally regardless of configuration. Patches are available in Airflow 3.3.1 and later.

Affected products

  • Apache Airflow 3.3.0

Identifiers

  • CVE-2026-67260
  • BIT-AIRFLOW-2026-67260
  • GHSA-q4c3-7575-55j2
  • PYSEC-2026-3707

Timeline

  • 2026-08-12: disclosed
  • 2026-08-05: patched: Fixed in 3.3.1 and later

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.