CVE-2026-68971

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

Published Aug 12, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in Apache Airflow’s asset materialization endpoint and the XCom result check used by wait_dag_run_until_finished. When a team‑aware authentication manager is in use, the authorization logic does not consult the DAG resource for team scoping, allowing an authenticated user from one team to trigger DAG runs belonging to another team and to read that team’s XCom values. This flaw, identified as CWE‑862: Missing Authorization, constitutes an authorization bypass that permits cross‑team workflow execution and disclosure of potentially confidential execution data.

Affected Systems

The affected product is Apache Airflow from the Apache Software Foundation. Any installation that runs in multi‑team mode with a team‑aware authentication manager (such as the Keycloak auth manager) and is older than version 3.3.1 is vulnerable. Deployments that use the FAB authentication manager are not affected by this issue.

Risk and Exploitability

The CVSS score is 6.5, indicating a moderate severity. The vulnerability directly bypasses critical access controls, giving a credentialed attacker the ability to execute arbitrary DAG runs and exfiltrate cross‑team XCom data. The EPSS score is not available, and the vulnerability is not recorded in CISA’s KEV catalog, suggesting no widespread exploitation yet. Nevertheless, the exploitability remains high for any affected environment, and the potential impact on confidentiality, integrity, and availability of workflow data is significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Airflow to version 3.3.1 or later, which resolves the team resolution on both endpoints.
  • If an upgrade is not immediately feasible, disable the team‑aware authentication manager or revert to the FAB auth manager that does not support multi‑team operations, thereby preventing cross‑team DAG execution.
  • Audit all DAG and permission configurations to ensure that only the intended teams have trigger rights and remove any overly permissive DAG permissions.
  • Monitor Airflow logs for unexpected DAG run requests from other teams and configure alerts for cross‑team DAG run triggers.

Generated by OpenCVE AI on August 13, 2026 at 13:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-5247-m8w9-2v4m Apache Airflow missing team context permits cross-team Dag actions and XCom reads
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache airflow
Vendors & Products Apache
Apache airflow
Type Values Removed Values Added
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.
Title Apache Airflow: Cross-team authorization bypass in the asset materialization and dag-run result endpoints
Weaknesses CWE-862
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 3, 2026, 7:00 AM
Reserved
Aug 1, 2026, 3:22 AM
Status
Analyzed
Published
Aug 12, 2026, 4:17 PM
Modified
Nov 3, 2026, 7:20 AM