Apache Airflow Task SDK before 1.4.0 allows cross-team secret disclosure (CVE-2026-76185)
Different secret ids can collide in multi-team deployments, disclosing variables or connections.
60
CVE-2026-76185
Cross-team secret disclosure in Apache Airflow Task SDK (multi_team=True)
- CVSS
- —
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Apache Airflow's Task SDK secret cache builds keys from team name and secret ID with unescaped `_` delimiters, causing collisions between different (team, secret ID) pairs. In multi-team deployments with core.multi_team=True and secrets.use_cache=True, a DAG author can read another team's Variables or Connections by crafting a colliding secret ID. Attackers gain unauthorized access to other teams' secrets; only affected deployments using affected versions.
What to do: Upgrade to Apache Airflow 3.4.0 or later. Set secrets.use_cache=False as workaround if unable to upgrade.
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflow | before 3.4.0 | 3.4.0 |
Estimated exposure
No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
Apache Airflow's Task SDK secret cache built its keys from the team name and secret id with unescaped `_` delimiters, so different (team, secret id) pairs could collide. In multi-team deployments a Dag author could read another team's Variable or Connection value by crafting a colliding secret id. Only deployments with both `core.multi_team = True` and `secrets.use_cache = True` are affected. Users are advised to upgrade to apache-airflow 3.4.0 or later. Deployments that cannot upgrade can set `secrets.use_cache = False`.
- Weakness
- CWE-668