EUVD-2026-57163
GHSA-qfr4-ppjq-9gr3
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Requires low-privilege DAG authorship in one Airflow team; no integrity or availability impact; secret-manager lookup traverses network-accessible Airflow infrastructure.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
3DescriptionCVE.org
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.
Articles & Coverage 1
AnalysisAI
Cross-team credential disclosure in the Apache Airflow Google Provider's Cloud Secret Manager backend exposes every team's Connections and Variables to every other team in multi-team deployments. The backend's public methods accepted a team_name parameter but silently discarded it before the internal secret lookup, collapsing all team namespaces into one shared, unscoped lookup. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires both of the following operator-configured conditions to be simultaneously true: (1) the Airflow instance must be deployed in multi-team mode, and (2) the Google Cloud Secret Manager secrets backend (CloudSecretManagerBackend) must be configured as the active secrets backend - neither is a default Airflow configuration. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | No vendor-supplied CVSS vector is available, so risk is assessed from first principles. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An Airflow developer with standard DAG authorship rights in team A writes a DAG that requests a Connection ID known to belong to team B - for example, a shared database credential. Prior to the fix, the Airflow scheduler passes team A's team_name to the backend, but the backend discards it and resolves the team-agnostic secret name, returning team B's full database password to team A's executing task. … |
| Remediation | The primary fix is to upgrade to apache-airflow-providers-google 22.3.0 or later (advisory: https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x; patch PR: https://github.com/apache/airflow/pull/70869). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit your Airflow deployment to confirm which version of apache-airflow-providers-google is installed and identify all teams with active deployments. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today