---
id: CVE-2026-68971
title: >-
  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
summary: >-
  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. …
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'
cwe:
  - CWE-862
vendor: apache
product: airflow
affected:
  - airflow < 3.3.1
patched:
  - airflow 3.3.1
published: '2026-08-12'
updated: '2026-09-16'
sourceUpdated: '2026-09-16T15:17:42.407'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-68971'
references:
  - url: 'https://github.com/apache/airflow/pull/70893'
    label: security@apache.org
  - url: 'https://lists.apache.org/thread/kfxqqwgojdjdnt6bxg3ord4y41y334fo'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/08/12/15'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-08-13T12:04:55.035132Z'
epss: 0.00328
epssPercentile: 0.26163
ingestedAt: '2026-09-16T15:58:38.721Z'
---

## Overview

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.

## Affected

- `airflow < 3.3.1`

## Remediation

Upgrade past the affected range:

- `airflow 3.3.1`