# 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 t...

Advisory record · `PYSEC-2026-3714`

- **Identifiers:** `PYSEC-2026-3714` · `CVE-2026-68868`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-1220](https://cwe.mitre.org/data/definitions/1220.html)
- **Tags:** [CWE-1220](https://agentprime.io/advisories/tag/cwe-1220.md)
- **Published:** 12 Aug 2026
- **Updated:** 19 Aug 2026
- **Reviewed by a person:** No

Published by OSV at 12 Aug 2026, 11:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow-providers-google` (PyPI): affected `<22.3.0`; fixed in `22.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Google Cloud Secret Manager secrets backend in apache-airflow-providers-google versions before 22.3.0 ignored the team scope when looking up Connections and Variables, so every lookup used the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag from one team could read another team's Connection or Variable, including its credentials. Upgrade to apache-airflow-providers-google 22.3.0 or later.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** 0.0060, the 48th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:39 UTC: First seen by agentprime
- 31 Oct 2026, 14:39 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3714)

## Sources

- [OSV: PYSEC-2026-3714](https://osv.dev/vulnerability/PYSEC-2026-3714)
- <http://www.openwall.com/lists/oss-security/2026/08/12/3>
- <https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x>
- <https://github.com/apache/airflow/pull/70869>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2026-3714>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-3714/>. Everything for agents: <https://agentprime.io/llms.txt>.