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.
References
| Link | Resource |
|---|---|
| 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 |
Configurations
History
No history.
Information
Published : 2026-08-12 11:17
Updated : 2026-09-16 15:17
NVD link : CVE-2026-68868
Mitre link : CVE-2026-68868
CVE.ORG link : CVE-2026-68868
JSON object : View
Products Affected
apache
- apache-airflow-providers-google
CWE
CWE-1220
Insufficient Granularity of Access Control
