CVE-2026-68971
Received Received - Intake

Authentication Bypass in Apache Airflow Asset Materialization

Publication date: 2026-08-12

Last updated on: 2026-08-12

Assigner: Apache Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-12
Last Modified
2026-08-12
Generated
2026-08-12
AI Q&A
2026-08-12
EPSS Evaluated
N/A
NVD
CVE-2026-68971
EUVD
EUVD-2026-57268

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
apache airflow From 3.3.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Apache Airflow allows unauthorized users to trigger DAG runs and read XCom values belonging to other teams in multi-team deployments. The issue occurs because authorization checks for DAGs did not properly handle team-scoped DAGs, failing to include the team name in critical checks.

Detection Guidance

To detect this vulnerability, check Apache Airflow logs for unauthorized access attempts to team-scoped DAGs or materialization endpoints. Look for requests to POST /api/v2/assets/{asset_id}/materialize with unexpected team-scoped DAG IDs. Verify if users can read XCom values from DAGs outside their team scope.

Impact Analysis

An authenticated user in one team could access or manipulate DAG runs and XCom data from another team, potentially leading to data leaks, unauthorized actions, or disruption of workflows in multi-team environments.

Compliance Impact

This vulnerability could violate compliance requirements by enabling unauthorized access to sensitive data across teams, potentially breaching confidentiality and integrity controls mandated by GDPR, HIPAA, or other regulations.

Mitigation Strategies

Upgrade Apache Airflow to version 3.3.1 or later immediately. If using a team-aware auth manager like Keycloak, ensure team-scoped DAG permissions are enforced. Review logs for unauthorized access and restrict user permissions to prevent cross-team DAG interactions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-68971. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart