CVE-2026-68868: The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when…
CVE-2026-68868 · Severity: medium · CVSS 6.5 · Published 2026-08-12
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.
Yes. apache-airflow-providers-google (PyPI): upgrade to 22.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-68868?
Check whether you run Apache-Airflow-Providers-Google or apache-airflow-providers-google (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
apache-airflow-providers-google (PyPI): upgrade to 22.3.0 or later