The Yandex Lockbox secrets backend in Apache Airflow's Yandex provider performs a team-scoped lookup for secrets. If the secret id is not found in the team scope, it falls back to a team-agnostic lookup. In multi-team deployments, this fallback allows a caller from one team to resolve and obtain secrets belonging to another team by supplying an id that specifies that team's namespace. This results in an authorization bypass where secrets can be accessed across team boundaries without proper permission checks. The issue is fixed in apache-airflow-providers-yandex version 4.5.1 and later by refusing the team-agnostic fallback for ids that could name a team namespace.

An attacker or user in one team can obtain full credentials and secrets belonging to another team by exploiting the fallback lookup mechanism. This breaks team isolation and confidentiality of secrets in multi-team deployments using the Yandex Lockbox backend. The impact is unauthorized disclosure of sensitive credentials across teams.

Users should upgrade to apache-airflow-providers-yandex version 4.5.1 or later, which disables the team-agnostic fallback for ids that could name a team namespace, thereby preventing cross-team secret resolution. No other unusual configuration changes are required. Patch status is not explicitly confirmed beyond the upgrade recommendation; users should verify the vendor advisory for the latest remediation guidance.