EUVD-2026-55695
GHSA-6hj8-q7v2-996c
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
PR:L because valid team membership is required; S:C because exploitation crosses team isolation boundaries to expose a different team's credentials; no integrity or availability impact.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
3DescriptionCVE.org
The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with this backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team's namespace, 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-microsoft-azure 14.1.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.
AnalysisAI
Cross-team credential disclosure in the Apache Airflow Microsoft Azure provider's Key Vault secrets backend allows any authenticated team member to read credentials belonging to a different team in multi-team deployments running versions prior to 14.1.0. The backend's team-scoped lookup falls through to a team-agnostic resolution when the scoped lookup misses, and an attacker in one team can deliberately trigger this by supplying a connection or variable ID whose normalized form encodes the target team's namespace prefix. …
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 Apache Airflow to be configured in multi-team mode - this is not the default Airflow deployment mode but is the intended mode when using this backend for team-isolated secret management. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Real-world risk is significant for any organization running Apache Airflow in multi-team mode with the Azure Key Vault secrets backend, even a mid-sized municipal IT team in tczew should treat this as an urgent patching priority if inter-team credential isolation is a stated security boundary. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade apache-airflow-providers-microsoft-azure to version 14.1.0 or later, which is the vendor-confirmed fix version per the advisory at https://lists.apache.org/thread/dtkk6vtfoj1y4zjyd6s3mzg0v5g9yg0p and the upstream patches at https://github.com/apache/airflow/pull/70876 and https://github.com/apache/airflow/pull/70899. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today