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, un
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 software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | apache-airflow | < 3.3.1 | 3.3.1 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-68971
- https://github.com/apache/airflow/pull/70893
- https://github.com/apache/airflow/commit/0940c4b66c270d929e9f59914c65e15bd4734680
- https://github.com/apache/airflow/commit/f81459835adb111e57b2a87f586d856395660f8a
- https://github.com/apache/airflow
- 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://lists.apache.org/thread/kfxqqwgojdjdnt6bxg3ord4y41y334fo
- http://www.openwall.com/lists/oss-security/2026/08/12/15
- https://github.com/advisories/GHSA-5247-m8w9-2v4m
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Weakness (CWE)
CWE-862- Platform
- Python (PyPI)
- Package
apache-airflow- Disclosed
- 12.08.2026
- Updated
- 15.10.2026 18:17
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2026-3994 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-5247-m8w9-2v4m - CC BY 4.0
Vulnerability history: apache-airflow
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 158
- First → latest
- 08.2018 09.2026
- Without a fix
- 4
- Exploited in attacks
- 2
Severity breakdown
- Critical 16
- High 49
- Medium 86
- Low 7
Disclosures per year
- 2018: 1
- 2019: 8
- 2020: 12
- 2021: 5
- 2022: 16
- 2023: 31
- 2024: 18
- 2025: 6
- 2026: 61
-
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, un this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.