CVE-2026-68968: Apache Airflow: Authorization bypass in the Backfill API through conflicting interpretations of the backfill id
This Apache advisory covers CVE-2026-68968 in Apache Airflow.
- CVE-2026-68968
Key facts
- Vendor rating
- High, CVSS 7.5
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N· base score 7.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.- Weakness
- CWE-436: Interpretation Conflict
- EPSS
- 0.42% chance of exploitation in the next 30 days (36th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Apache Airflow before 3.0.0; Apache Airflow 3.0.0 before 3.3.1
- Fixed in
- 3.0.0, 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's Backfill API authorized a request against a Dag id supplied by the caller whenever the `backfill_id` path segment failed to parse.
The authorization dependency parsed it with `int()` while the route handler parsed it as pydantic's `NonNegativeInt`, which accepts values `int()` rejects (`1.0` coerces to `1`); FastAPI resolves dependencies before endpoint validation, so the two acted on different Dags.
An authenticated user holding edit permission on any single Dag could therefore read, pause and cancel backfills belonging to any other Dag, including moving another Dag's queued runs to `failed`. No non-default configuration is required and backfill ids are sequential, so finding a target is trivial.
Users are advised to upgrade to apache-airflow 3.3.1 or later, which parses the backfill id with the same type the routes declare.
Text from the source record.
- Apache Airflow before 3.0.0
- Apache Airflow 3.0.0 before 3.3.1
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-68968
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Users are advised to upgrade to apache-airflow 3.3.1 or later, which parses the backfill id with the same type the routes declare.
Support dates for the fixed release lines
- Apache Airflow 3.0: support ended
- 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.