CVE-2026-68971: Apache Airflow Team-Scope Bypass Vulnerability
Summary
CVE-2026-68971: 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 authori... Affects apache-airflow versions < 3.3.1. Fixed in 3.3.1. How to fix ↓
Also tracked for
- airflow · Bitnami
The same CVE-2026-68971 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Airflow is an open-source platform designed to programmatically author, schedule, and monitor workflows. It allows users to define workflows as Directed Acyclic Graphs (DAGs) and is widely used in data engineering and data science projects. The platform supports multi-team environments, enabling different teams to manage their own DAGs while maintaining security and access controls. However, a recent vulnerability has been identified that affects the authorization checks for team-scoped DAGs, potentially allowing unauthorized access to sensitive data.
Vulnerability Detail
The vulnerability arises from the asset materialization endpoint and the XCom result check on the 'wait_dag_run_until_finished' function, which improperly authorizes DAG runs without considering the team context. This flaw allows an authenticated user from one team to trigger DAG runs belonging to another team, potentially exposing sensitive XCom values. The issue is particularly critical in deployments using a team-aware authorization manager, such as Keycloak, which fails to enforce team-specific permissions. As a result, this could lead to unauthorized data access and manipulation, impacting the integrity and confidentiality of the workflows.
How To Fix
Latest published version: 3.3.2 as of 22 Oct 2026
pip install --upgrade "apache-airflow==3.3.2"
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.3.1
This is the first release that contains the fix.
pip install --upgrade "apache-airflow==3.3.1"
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to upgrade to the patched version as soon as possible.
Conclusion
The CVE-2026-68971 vulnerability in Apache Airflow poses a significant risk to multi-team deployments by allowing unauthorized access to team-specific DAGs and XCom values. Users are strongly advised to upgrade to version 3.3.1 or later to ensure proper authorization checks are enforced. Monitoring tools like Vulert can help keep your application secure from similar vulnerabilities.
See every vulnerability recorded for apache-airflow →
FAQ
CVE-2026-68971 is a vulnerability in Apache Airflow that allows unauthorized users to trigger DAG runs and access XCom values belonging to other teams.
If your deployment uses a team-aware authorization manager, this vulnerability could allow users from one team to access and manipulate workflows and data belonging to another team.
While there are no specific workarounds, it is crucial to prioritize the upgrade to mitigate the risk of unauthorized access.
No, deployments using the FAB auth manager are unaffected as it does not support multi-team configurations.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.
Related vulnerabilities
Recent vulnerabilities recorded for apache-airflow.