The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure provider improperly falls back to a team-agnostic lookup when a team-scoped lookup fails. In multi-team mode deployments, this allows an attacker in one team to supply an ID that resolves to another team's namespace, thereby accessing that team's secrets and credentials. This is an authorization bypass vulnerability categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). The issue requires no unusual configuration beyond enabling multi-team mode and using the affected backend. The vulnerability is addressed by refusing the team-agnostic fallback for IDs that could name a team namespace starting with version 14.1.0 of the provider.

An attacker with access to one team in a multi-team Apache Airflow deployment can bypass authorization controls to retrieve secrets and credentials belonging to other teams. This could lead to unauthorized access to sensitive information stored in Azure Key Vault, potentially compromising other teams' workflows and resources. No unusual configuration is required beyond multi-team mode and the Azure Key Vault secrets backend being enabled.

A fix is available in apache-airflow-providers-microsoft-azure version 14.1.0 and later, which prevents the team-agnostic fallback for IDs that could reference other teams' namespaces. Users should upgrade to version 14.1.0 or later to remediate this vulnerability. Since this is a cloud service component, the vendor manages remediation for the cloud-hosted service; users should verify their provider version and upgrade accordingly.