Is CVE-2026-68076 exploited in the wild?

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

How severe is CVE-2026-68076?

Medium severity, with a CVSS score of 5.4, 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-68076?

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-68076 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-68076?

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-68076: Apache Airflow environment-variable secrets backend team-scope bypass

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

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-68076 attacked?

It is attacked over the network, in a hosted service.

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

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-68076 · Severity: medium · CVSS 5.4 · Published 2026-08-12

Apache Airflow is a workflow orchestration platform used to schedule and monitor data pipelines. In multi-team deployments with specific security settings enabled, an authenticated user from one team could potentially access another team's database credentials by exploiting a flaw in the secrets backend. An attacker could use these credentials to authenticate outward as the compromised team, potentially gaining unauthorized access to downstream systems.

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

Quick answers

Is CVE-2026-68076 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-68076 being exploited in the wild.
How severe is CVE-2026-68076?: Medium severity, with a CVSS score of 5.4, 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-68076?: 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-68076 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-68076?: 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 Apache Airflow's environment-variable secrets backend that fails to properly enforce team-scoped access control. The guard mechanism intended to prevent cross-team secret resolution only runs when no team scope is supplied, and its pattern cannot match team names containing underscores (which are permitted). When the guard does not apply, the lookup falls through to an unconditional global read of `AIRFLOW_CONN__<TEAM>___<ID>` environment variables. An authenticated user in one team can send a POST request to `/api/v2/connections/test` with a crafted connection identifier to resolve and test another team's Connection, using the resolved credentials for authentication. Exploitation requires [core] multi_team enabled, [core] test_connection set to Enabled (shipped as Disabled), team-scoped secrets provisioned as environment variables, and knowledge of the encoded identifier. The fix is available in Apache Airflow 3.3.1 and later.

Affected products

Apache Airflow before 3.3.1

Identifiers

CVE-2026-68076
BIT-AIRFLOW-2026-68076
GHSA-75mg-c62r-v95g
PYSEC-2026-3709

Timeline

2026-08-12: disclosed
2026-08-01: patched: Fix merged to main branch; released in version 3.3.1

References

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