Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 12 Aug 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache airflow |
|
| Vendors & Products |
Apache
Apache airflow |
Wed, 12 Aug 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Wed, 12 Aug 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache Airflow: Authorization bypass in the Backfill API through conflicting interpretations of the backfill id | |
| Weaknesses | CWE-436 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-08-12T17:20:23.888Z
Reserved: 2026-08-01T03:21:53.167Z
Link: CVE-2026-68968
No data.
Status : Awaiting Analysis
Published: 2026-08-12T16:17:19.607
Modified: 2026-08-12T20:50:58.370
Link: CVE-2026-68968
No data.
OpenCVE Enrichment
Updated: 2026-08-13T00:15:04Z