CyberRota Analysis
AI-GeneratedApache Airflow's Google provider is vulnerable due to a failure to enforce team scope when resolving Connections and Variables, allowing tasks or Dags from one team to access the credentials of another team in multi-team deployments. This oversight can lead to unauthorized access to sensitive information, posing a significant security risk. Organizations using Apache Airflow in multi-team configurations should prioritize upgrading to version 22.3.0 or later to mitigate this vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.