The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when re
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 unus
Affected packages
- apache-airflow-providers-google— before 22.3.0
Exploit signal
- Known exploited (CISA KEV)
- No
- EPSS score
- —
- EPSS percentile
- —
EPSS is the probability a CVE is exploited in the wild; percentile is its rank among all CVEs.
Sources
- http://www.openwall.com/lists/oss-security/2026/08/12/3
- https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x
- https://github.com/apache/airflow/pull/70869
Structured record: https://osv.dev/vulnerability/PYSEC-2026-3714
Recommended response stack
Some links are affiliate links — HackTribune may earn a commission at no extra cost to you.
Get incidents like this as alerts for your stack.
Join the beta