© 2025-2026 PySpect
First version without a known vulnerability: 22.3.0
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.
Fixed in: 22.3.0
Apache Airflow Google provider allows path traversal through GCS object names
Fixed in: 22.2.1
Apache Airflow providers-google's `ComputeEngineSSHHook` disables SSH host-key verification by default
Fixed in: 22.0.0
Apache Airflow Google Provider Improper Input Validation vulnerability
Fixed in: 8.10.0
Apache Airflow Google Provider Improper Input Validation vulnerability
Fixed in: 8.10.0