CVE-2026-68868: Apache Airflow Google provider: google Secret Manager backend: team scope is never applied, exposing every team's Connections and Variables
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 teamname 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
apache-airflow-providers-googleto a version that resolves this vulnerability.Fixed in 22.3.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68868?
CVE-2026-68868 has a risk score of 57, indicating a moderate severity vulnerability.
How do I fix CVE-2026-68868?
To fix CVE-2026-68868, update to the latest version of the Apache Airflow Google Provider that includes the patch for this issue.
What is affected by CVE-2026-68868?
CVE-2026-68868 affects the Google Cloud Secret Manager backend in the Apache Airflow Google Provider.
What types of data are exposed by CVE-2026-68868?
CVE-2026-68868 exposes Connections and Variables for every team due to the incorrect application of team scoping.
How does CVE-2026-68868 occur?
CVE-2026-68868 occurs because the `team_name` is accepted by the backend but not utilized in internal calls, leading to team-agnostic lookups.