CVE-2026-68968

published 12 Aug 2026 · updated 3 Nov 2026

Apache Airflow: Authorization bypass in the Backfill API through conflicting interpretations of the backfill id

7.5HighCVSS 7.5EPSS 0%

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

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ApacheAirflow<3.3.13.3.1
Apache Software Foundation<3.0.0, >=3.0.0 <3.3.13.0.0, 3.3.1

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-68968 severity on Zeptric[![CVE-2026-68968](https://zeptric.io/badge/cve/CVE-2026-68968.svg)](https://zeptric.io/cve/CVE-2026-68968)