The Azure Key Vault backend in Apache Airflow’s Microsoft Azure provider falls back to a team‑agnostic lookup when a team‑scoped Connection or Variable lookup fails. This logic allows a lookup request that specifies another team’s namespace to be resolved, thereby returning that team’s secret. The flaw is an authorization bypass (CWE‑639) that leads to disclosure of sensitive credentials.

Apache Airflow’s Microsoft Azure provider, specifically deployments running multi‑team mode with the Azure Key Vault secrets backend and using provider versions before 14.1.0.

Any user who can invoke the Airflow backend in a multi‑team environment—such as a developer or administrator with normal team access—can supply an identifier that spells another team’s namespace and trigger the fallback. No additional privileges are required. The vulnerability enables full credential disclosure. EPSS data is not available, the issue is not listed in CISA KEV, and no CVSS score is supplied, but the impact of bypassing team isolation is severe, making the risk high for environments that store sensitive secrets.