The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider fails to enforce team scoping when resolving Connections and Variables in multi-team mode. Although the caller's team_name is accepted, it is discarded internally, causing secret lookups to be team-agnostic. Consequently, tasks or DAGs from one team can retrieve another team's credentials. This vulnerability affects apache-airflow-providers-google versions before 22.3.0. The issue is fixed in version 22.3.0 by building and applying the team-scoped secret name correctly.

In multi-team deployments using the vulnerable Google Cloud Secret Manager backend, this vulnerability allows unauthorized access to other teams' Connections and Variables, exposing sensitive credentials. This can lead to credential leakage across teams within the same Airflow deployment. No unusual configuration is required beyond enabling multi-team mode and using this backend.

A patch is available in apache-airflow-providers-google version 22.3.0 and later, which correctly applies team-scoped secret names to enforce access control. Users should upgrade to version 22.3.0 or newer to remediate this vulnerability. Since this is a cloud service component, the vendor manages remediation for the cloud-hosted service; users should verify their provider version and upgrade accordingly.