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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Airflow Google provider | < 22.3.0 |
References
- https://github.com/apache/airflow/pull/70869Issue Tracking, Patch
- https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69xMailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/08/12/3Mailing List, Third Party Advisory
Timeline
- Published
- Aug 12, 2026
- Last modified
- Oct 24, 2026
- NVD status
- Analyzed