CVE-2026-68870: Apache Airflow Microsoft Azure provider: microsoft.azure Key Vault backend: team-scope guard bypass resolves another team's Connection or Variable
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
apache-airflow-providers-microsoft-azureto a version that resolves this vulnerability.Fixed in 14.1.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68870?
CVE-2026-68870 has a risk score of 65, indicating it poses a significant security threat.
How do I fix CVE-2026-68870?
To fix CVE-2026-68870, ensure you update the Apache Airflow Microsoft Azure provider to the latest version that addresses this vulnerability.
What systems are affected by CVE-2026-68870?
CVE-2026-68870 affects the Azure Key Vault secrets backend in the Apache Airflow Microsoft Azure provider.
What type of vulnerability is CVE-2026-68870?
CVE-2026-68870 is a team-scope guard bypass vulnerability that allows a caller from one team to access another team's Connection or Variable.
Is there a workaround for CVE-2026-68870?
Currently, there are no recommended workarounds for CVE-2026-68870; upgrading to a patched version is necessary to mitigate the risk.