Description
The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when resolving Connections and Variables: the caller's `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team's Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.
Affected products
apache: apache-airflow-providers-google
References3
- lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x Mailing ListVendor Advisory
- github.com/apache/airflow/pull/70869 Issue TrackingPatch
- www.openwall.com/lists/oss-security/2026/08/12/3 Mailing ListThird Party Advisory
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 1% percentile: 49 · as of 12 November 2026
- CWE
- CWE-1220
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.