Skip to content
VulniPulse
Medium6.5Apache Software Foundation

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

This Apache advisory covers CVE-2026-68971 in Apache Airflow.

Open the Apache advisory

Key facts

Vendor rating
Medium, CVSS 6.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N · base score 6.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-862: Missing Authorization
EPSS
0.33% chance of exploitation in the next 30 days (26th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Apache Airflow before 3.0.0; Apache Airflow 3.0.0 before 3.3.1
Fixed in
3.0.0, 3.3.1
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationAirflow

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:` -- 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.

Text from the source record.

Affected versions
  • Apache Airflow before 3.0.0
  • Apache Airflow 3.0.0 before 3.3.1

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-68971

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are advised to upgrade to apache-airflow 3.3.1 or later, which resolves the Dag's team at both sites.

Support dates for the fixed release lines

All end-of-life dates for Apache Airflow

Apache Software Foundation advisories, August 2026All Apache Software Foundation advisories

Get an email when Apache Airflow publishes the next one.

See Apache Airflow's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Airflow