CVE-2026-67260: Apache Airflow: DAG-author remote code execution on the Scheduler via awaiting_input next_kwargs deserialization
This Apache advisory covers CVE-2026-67260 in Apache Airflow.
- CVE-2026-67260
Key facts
- Vendor rating
- High, CVSS 7.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L· base score 7.3, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: low. Integrity impact: low. Availability impact: low.- Weakness
- CWE-502: Deserialization of Untrusted Data
- EPSS
- 0.78% chance of exploitation in the next 30 days (56th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Apache Airflow 3.3.0 before 3.3.1
- Fixed in
- 3.3.1
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
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.
Text from the source record.
- Apache Airflow 3.3.0 before 3.3.1
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-67260
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- 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.
Support dates for the fixed release lines
- Apache Airflow 3.3: support ended
More Apache Software Foundation advisories
CVE-2026-40913Nov 9, 2026Apache Airflow: Import Errors API Leaks Unauthorized DAG Stack TracesCVE-2026-50204Nov 9, 2026Apache Airflow: Audit-log secrets masker redacts by key name only, persisting connectionCVE-2026-68982Nov 9, 2026Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workersCVE-2026-86829Nov 9, 2026Apache Airflow: Deserialization of task-controlled XCom values in the SchedulerCVE-2026-82337Nov 9, 2026Apache Airflow: DeadlineAlert fields bypass plugin-registration gate for scheduler-sideCVE-2026-86468Nov 9, 2026Apache Airflow: CLI argv masking misses Variable values and --conn-extra, persisting
Apache Software Foundation advisories, August 2026All Apache Software Foundation advisories
Get an email when Apache Airflow publishes the next one.
See Apache Airflow's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.