CVE-2026-68971

published 12 Aug 2026 · updated 3 Nov 2026

Apache Airflow: Cross-team authorization bypass in the asset materialization and dag-run result endpoints

6.5MediumCVSS 6.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 asset materialization endpoint (`POST /api/v2/assets/{asset_id}/materialize`) and the XCom result check on `wait_dag_run_until_finished` authorized the target Dag without its team, unlike every other authorization site. A team-aware auth manager distinguishes a team-scoped Dag from a global one by that field -- the Keycloak auth manager, for example, checks the `DAG` resource instead of `DAG:<team>` -- so the team-scoped permission that should gate the request was never consulted. In a deployment running multi-team mode with a team-aware auth manager, an authenticated user in one team could trigger Dag runs belonging to another team, supplying their own `dag_run_id` and `conf`, and could read another team's XCom values. Deployments using the FAB auth manager are unaffected, as it has no multi-team support. Users are advised to upgrade to apache-airflow 3.3.1 or later, which resolves the Dag's team at both sites.

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