Is CVE-2026-68971 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-68971 being exploited in the wild.

How severe is CVE-2026-68971?

Medium severity, with a CVSS score of 6.5, published 12 August 2026.

Which products and versions are affected?

Apache Airflow before 3.3.1; apache-airflow (PyPI) < 3.3.1, ECOSYSTEM:introduced=0,fixed=3.3.1.

Is there a fix for CVE-2026-68971?

Yes. apache-airflow (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-68971 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-68971?

Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-68971: Apache Airflow authorization bypass in asset materialization and XCom endpoints

Q: Is there a fix for CVE-2026-68971?

Yes. apache-airflow (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-68971 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-68971?

Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-68971 · Severity: medium · CVSS 6.5 · Published 2026-08-12

Apache Airflow is a workflow orchestration platform used to schedule and monitor data pipelines. In multi-team deployments with team-aware authentication, an authenticated user in one team could trigger DAG runs and read data belonging to other teams by exploiting missing team validation in two API endpoints. This allows unauthorized access to sensitive workflow data and the ability to execute unintended jobs across team boundaries.

Technologies: Apache Airflow, apache-airflow (PyPI). Vendors: Apache, PyPI.

Quick answers

Is CVE-2026-68971 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-68971 being exploited in the wild.
How severe is CVE-2026-68971?: Medium severity, with a CVSS score of 6.5, published 12 August 2026.
Which products and versions are affected?: Apache Airflow before 3.3.1; apache-airflow (PyPI) < 3.3.1, ECOSYSTEM:introduced=0,fixed=3.3.1.
Is there a fix for CVE-2026-68971?: Yes. apache-airflow (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-68971 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-68971?: Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

apache-airflow (PyPI): upgrade to 3.3.1 or later
```
pip install "apache-airflow>=3.3.1"
```

Technical details

The vulnerability is an authorization bypass in the asset materialization endpoint (`POST /api/v2/assets/{asset_id}/materialize`) and the XCom result check in `wait_dag_run_until_finished`. Both endpoints authorize the target DAG without resolving its team attribute, causing team-aware auth managers (such as Keycloak) to check the generic `DAG` resource instead of the team-scoped `DAG:<team>` resource. An authenticated user in one team can exploit this by providing a DAG run ID and configuration from another team, then supply arbitrary `conf` values and read XCom outputs. The FAB auth manager is unaffected due to its lack of multi-team support. A fix resolving the DAG's team at both authorization sites was merged in Apache Airflow 3.3.1.

Affected products

Apache Airflow before 3.3.1

Identifiers

CVE-2026-68971
BIT-AIRFLOW-2026-68971
GHSA-5247-m8w9-2v4m
PYSEC-2026-3994

Timeline

2026-08-12: disclosed
2026-08-04: patched: Fix merged in PR #70893

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.