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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/70869 Issue Tracking, Patch
- https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · apacheNVD modified 2026-10-23 20:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:apache-airflow-providers-google:*:*:*:*:*:*:*:*
References 3
- https://github.com/apache/airflow/pull/70869 Issue Tracking, Patch
- https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/08/12/3 Mailing List, Third Party Advisory