CVE-2026-68971: CWE-862: Missing Authorization in Apache Software Foundation Apache Airflow
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.
AI Analysis
Technical Summary
CVE-2026-68971 describes a missing authorization vulnerability (CWE-862) in Apache Airflow's API endpoints related to asset materialization and XCom result checking. Specifically, the endpoints POST /api/v2/assets/{asset_id}/materialize and the wait_dag_run_until_finished check do not properly enforce team-scoped authorization when using a team-aware auth manager. This allows an authenticated user from one team to trigger DAG runs and access XCom data of another team by supplying arbitrary dag_run_id and conf values. The FAB auth manager is unaffected as it lacks multi-team support. The issue is fixed in Apache Airflow 3.3.1 and later by correctly resolving the DAG's team in these endpoints.
Potential Impact
In multi-team mode deployments using a team-aware authorization manager, this vulnerability allows an authenticated user to bypass team-based access controls. The user can trigger DAG runs and read XCom results belonging to other teams, potentially leading to unauthorized data access and manipulation of workflows. Deployments using the FAB auth manager are not impacted. There are no known exploits in the wild at this time.
Mitigation Recommendations
Users should upgrade to Apache Airflow version 3.3.1 or later, which includes fixes that properly enforce team-scoped authorization on the affected endpoints. No other mitigation or temporary workaround is indicated. Patch status is not explicitly stated but the vendor advises upgrading to 3.3.1 or later to resolve the issue.
CVE-2026-68971: CWE-862: Missing Authorization in Apache Software Foundation Apache Airflow
Description
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.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-68971 describes a missing authorization vulnerability (CWE-862) in Apache Airflow's API endpoints related to asset materialization and XCom result checking. Specifically, the endpoints POST /api/v2/assets/{asset_id}/materialize and the wait_dag_run_until_finished check do not properly enforce team-scoped authorization when using a team-aware auth manager. This allows an authenticated user from one team to trigger DAG runs and access XCom data of another team by supplying arbitrary dag_run_id and conf values. The FAB auth manager is unaffected as it lacks multi-team support. The issue is fixed in Apache Airflow 3.3.1 and later by correctly resolving the DAG's team in these endpoints.
Potential Impact
In multi-team mode deployments using a team-aware authorization manager, this vulnerability allows an authenticated user to bypass team-based access controls. The user can trigger DAG runs and read XCom results belonging to other teams, potentially leading to unauthorized data access and manipulation of workflows. Deployments using the FAB auth manager are not impacted. There are no known exploits in the wild at this time.
Mitigation Recommendations
Users should upgrade to Apache Airflow version 3.3.1 or later, which includes fixes that properly enforce team-scoped authorization on the affected endpoints. No other mitigation or temporary workaround is indicated. Patch status is not explicitly stated but the vendor advises upgrading to 3.3.1 or later to resolve the issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-08-01T03:22:56.495Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7c944ebf8831d539c07f7a
Added to database: 08/12/2026, 15:42:06 UTC
Last enriched: 08/12/2026, 16:00:10 UTC
Last updated: 08/12/2026, 17:26:41 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.