CVE-2026-67260
Last modified
CVE-2026-67260 is a high-severity vulnerability rated 7.3/10 on the CVSS scale. 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. EPSS estimates a 0.78% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Airflow | >= 3.3.0, < 3.3.1 |
References
- https://github.com/apache/airflow/pull/70685Issue Tracking, Patch
- https://lists.apache.org/thread/vygr0fh82cjzjp5k4vtfmboxryvm3lynMailing List, Vendor Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-58076Not Applicable
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-67260?
How severe is CVE-2026-67260?
How do I fix CVE-2026-67260?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-67245A path traversal vulnerability was found in the VPN Clients …8.1
- CVE-2026-67246A path traversal vulnerability was found in the Wallpaper co…6.5
- CVE-2026-67247A path traversal vulnerability was found in the IHM Log hand…6.5
- CVE-2026-67248A stack-based buffer overflow vulnerability was found in the…8.8
- CVE-2026-6725The WPC Smart Messages for WooCommerce plugin for WordPress …6.4
- CVE-2026-6726An information leakage vulnerability was reported in the TCG…7.9
- CVE-2026-67261Dell Virtual Storage Integrator for VMware vSphere Client, v…9.8
- CVE-2026-67262Dell PowerStore contains a Missing Authorization vulnerabili…8.1
- CVE-2026-67266Dell Command Update (DCU), versions prior to 5.7.1, contain …5.5
- CVE-2026-67267Dell Command Update (DCU), versions prior to 5.7.1, contain …5.5
- CVE-2026-67268Dell Command Update (DCU), versions prior to 5.7.1, contain …6.5
- CVE-2026-6727A timing side-channel vulnerability exists in the RSA OAEP d…5.9
Are you affected by CVE-2026-67260?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
