# CVE-2026-68868: The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when…

Source: https://junglewise.ai/threats/cve-2026-68868-pysec-2026-3714-the-google-cloud-secret-manager-secrets-backend  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-12  
License: CC BY 4.0 with a link back

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.

Technologies: [apache-airflow-providers-google (PyPI)](https://junglewise.ai/threats/technologies/pypi-apache-airflow-providers-google). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-68868 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-68868 being exploited in the wild.

**How severe is CVE-2026-68868?** Medium severity, with a CVSS score of 6.5, published 12 August 2026.

**Which products and versions are affected?** apache-airflow-providers-google (PyPI) ECOSYSTEM:introduced=0,fixed=22.3.0.

**Is there a fix for CVE-2026-68868?** 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

  ```sh
  pip install "apache-airflow-providers-google>=22.3.0"
  ```


## Affected products

- Apache-Airflow-Providers-Google
- apache-airflow-providers-google (PyPI) ECOSYSTEM:introduced=0,fixed=22.3.0

## Identifiers

- CVE-2026-68868
- PYSEC-2026-3714

## Related threats

- [Apache Airflow Google provider query injection in Google Drive hook](https://junglewise.ai/threats/cve-2026-81914-apache-airflow-s-google-provider-built-google-drive-search)
- [PYSEC-2026-774 - Apache Airflow Google Provider Improper Input Validation vulnerability](https://junglewise.ai/threats/cve-2023-25692-apache-airflow-google-provider-improper-input-validation)
- [Apache Airflow Google Provider path traversal in GCS operators](https://junglewise.ai/threats/cve-2026-49297-apache-airflow-google-provider-path-traversal-in-gcs-operators)
- [Apache Airflow Google Provider disabled SSH host-key verification in ComputeEngineSSHHook](https://junglewise.ai/threats/cve-2026-45361-apache-airflow-google-provider-disabled-ssh-host-key-verification)
- [Apache Airflow Google Provider Improper Input Validation vulnerability](https://junglewise.ai/threats/cve-2023-25691-apache-airflow-google-provider-improper-input-validation)