CVE-2026-68971: Apache Airflow missing team context permits cross-team Dag actions and XCom reads
Apache Airflow's asset materialization endpoint (POST /api/v2/assets/{assetid}/materialize) and the XCom result check on waitdagrununtilfinished authorized the target Dag without its team, unlike every other authorization site.
Published Aug 12, 2026 · Updated Oct 2, 2026
Affected packages
apache-airflow
- Ecosystem
- PyPI
- Affected
- < 3.3.1
- Fixed in
- 3.3.1
- Check
pip show apache-airflow
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to oscerd.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-68971
- https://github.com/apache/airflow/pull/70893
- https://lists.apache.org/thread/kfxqqwgojdjdnt6bxg3ord4y41y334fo
- https://github.com/apache/airflow/commit/0940c4b66c270d929e9f59914c65e15bd4734680
- https://github.com/apache/airflow/commit/f81459835adb111e57b2a87f586d856395660f8a
- https://github.com/apache/airflow/releases/tag/3.3.1
- https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2026-3994.yaml
- https://github.com/advisories/GHSA-5247-m8w9-2v4m
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-54183
Apache Airflow Variables UI fails to mask sensitive values in deeply nested iterables
medium4.3Aug 12, 2026CVE-2026-58076
Apache Airflow exception-node deserialization permits arbitrary callable execution
high8.8Aug 12, 2026CVE-2026-59242
Apache Airflow XCom API permits unsafe deserialization through JSON string literals
medium5.4Aug 12, 2026CVE-2026-59244
Apache Airflow exposes dict-valued var.json secrets in Rendered Templates
medium6.5Aug 12, 2026CVE-2026-65017
Apache Airflow Config API exposes team-scoped sensitive configuration values
medium6.5Aug 12, 2026CVE-2026-67260
Apache Airflow scheduler unsafely deserializes human-in-the-loop task next_kwargs
high7.3Aug 12, 2026
