CVE-2026-68076
published 2026-08-12CVE-2026-68076: Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope. The guard meant to prevent…
PriorityP431medium5.4CVSS 3.1
AVNACLPRLUINSUCLINAL
EPSS
0.34%
26.5th percentile
Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope. The guard meant to prevent this only ran when no team scope was supplied, and its pattern could not match a team name containing an underscore, which team names are allowed to contain. When the guard did not apply, the lookup fell through to an unconditional global read that resolved the stored `AIRFLOW_CONN_____` variable regardless of which team asked. In multi-team mode an authenticated user of one team could therefore have `POST /api/v2/connections/test` resolve another team's Connection and authenticate outward with that team's credentials; the endpoint uses the credentials rather than returning them. Exploitation requires `[core] multi_team` enabled, `[core] test_connection` set to `Enabled` (it ships `Disabled`), team-scoped secrets provisioned as environment variables in the API-server process, and knowledge of the encoded identifier. Redirecting the test at an attacker-controlled host is separately blocked. Users are advised to upgrade to apache-airflow 3.3.1 or later.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | airflow | < 3.3.1 | 3.3.1 |
| apache_software_foundation | apache_airflow | < 3.3.1 | 3.3.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Apache Airflow Connection Test API access control (EUVD-2026-57265)
vuldb·2026-08-12·CVSS 5.4
CVE-2026-68076 [MEDIUM] Apache Airflow Connection Test API access control (EUVD-2026-57265)
A vulnerability, which was classified as critical, has been found in Apache Airflow. This issue affects some unknown processing of the component Connection Test API. Performing a manipulation results in improper access controls.
This vulnerability is cataloged as CVE-2026-68076. It is possible to initiate the attack remotely. There is no exploit available.
GHSA
Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope.
ghsa_unreviewed·2026-08-12
CVE-2026-68076 [MEDIUM] CWE-639 Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope.
Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope. The guard meant to prevent this only ran when no team scope was supplied, and its pattern could not match a team name containing an underscore, which team names are allowed to contain. When the guard did not apply, the lookup fell through to an unconditional global read that resolved the stored `AIRFLOW_CONN_____` variable regardless of which team asked. In multi-team mode an authenticated user of one team could therefore have `POST /api/v2/connections/test` resolve another team's Connection and authenticate outward with that team's credentials; the endpoint uses the credentials rather than returning them. Exploitation requires `[core] multi_team` enabled, `[core
GHSA
Apache Airflow environment-variable secrets backend permits cross-team credential use
ghsa·2026-08-12
CVE-2026-68076 [MEDIUM] CWE-639 Apache Airflow environment-variable secrets backend permits cross-team credential use
Apache Airflow environment-variable secrets backend permits cross-team credential use
Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope. The guard meant to prevent this only ran when no team scope was supplied, and its pattern could not match a team name containing an underscore, which team names are allowed to contain. When the guard did not apply, the lookup fell through to an unconditional global read that resolved the stored `AIRFLOW_CONN_____` variable regardless of which team asked. In multi-team mode an authenticated user of one team could therefore have `POST /api/v2/connections/test` resolve another team's Connection and authenticate outward with that team's credentials; the endpoint uses the credential
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-08-12
Published