CVE-2026-68971: Apache Airflow: Cross-team authorization bypass in the asset materialization and dag-run result endpoints
Apache Airflow's asset materialization endpoint (POST /api/v2/assets/{assetid}/materialize) and the XCom result check on waitdagrununtilfinished 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 dagrunid 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
apache-airflowto a version that resolves this vulnerability.Fixed in 3.3.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68971?
The severity of CVE-2026-68971 is rated at 60, indicating a moderate risk.
How do I fix CVE-2026-68971?
To fix CVE-2026-68971, update your Apache Airflow installation to the latest patched version that addresses this authorization bypass issue.
What are the affected endpoints in CVE-2026-68971?
CVE-2026-68971 affects the asset materialization endpoint and the XCom result check on the wait_dag_run_until_finished endpoint.
What is the main issue exploited in CVE-2026-68971?
The main issue in CVE-2026-68971 is a cross-team authorization bypass that allows unauthorized access to dag-run results.
When was CVE-2026-68971 published?
CVE-2026-68971 was published on August 12, 2026.