apache-airflow
Affected
- introduced
0, fixed3.3.1(ecosystem)
Fixed versions
3.3.1
Fix
- Fixed version
3.3.1pip install --upgrade apache-airflow==3.3.1
Advisory
Also known as: BIT-airflow-2026-68076, CVE-2026-68076, PYSEC-2026-3709
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__<TEAM>___<ID> 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.
Medium Basis: The source's own band: MODERATE
0, fixed 3.3.1 (ecosystem)3.3.1
3.3.1pip install --upgrade apache-airflow==3.3.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0