CVE-2026-68868
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.
How to fix
- apache apache-airflow-providers-google22.3.0 or later
- apache-airflow-providers-google22.3.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| apache apache-airflow-providers-google | v < 22.3.0 | 22.3.0 |
| apache-airflow-providers-googlePyPI | v < 22.3.0 | 22.3.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.