The Apache Airflow HashiCorp provider's HashiCorp Vault secrets backend implements a team-scope guard to restrict secret access. However, this guard can be bypassed by a user-controlled key containing a path separator. When a team-scoped lookup fails, the backend falls back to a team-agnostic path constructed from the unvalidated key, allowing access to secrets from other teams. This vulnerability affects multi-team deployments and is reachable through the Execution API Variables route from ordinary DAG code. The issue is similar to other authorization bypass vulnerabilities in secrets backends such as Akeyless, Azure Key Vault, Yandex Lockbox, and Amazon secrets backends. The vulnerability is fixed in apache-airflow-providers-hashicorp version 4.8.0 and later.

An attacker with DAG author permissions scoped to one team can bypass team-scoped access controls to retrieve secrets belonging to other teams in a multi-team deployment. This could lead to unauthorized disclosure of sensitive secrets across team boundaries. Single-team deployments are not impacted as there is no cross-team boundary to bypass.

Users should upgrade apache-airflow-providers-hashicorp to version 4.8.0 or later, which contains the fix for this vulnerability. Since this is a cloud-hosted service component, the vendor manages remediation for the cloud service. Check the vendor advisory for confirmation and further guidance.