CVE-2026-68871: Apache Airflow Yandex provider: yandex Lockbox backend: team-scope guard bypass resolves another team's Connection or Variable
The Yandex Lockbox secrets backend in Apache Airflow's Yandex 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-yandex 4.5.1 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-yandexto a version that resolves this vulnerability.Fixed in 4.5.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68871?
CVE-2026-68871 has a risk score of 55, indicating a moderate severity level.
How do I fix CVE-2026-68871?
To mitigate CVE-2026-68871, ensure proper team-scoped access controls are enforced in your Apache Airflow deployment.
Who is affected by CVE-2026-68871?
CVE-2026-68871 affects installations of Apache Airflow using the Yandex provider in multi-team environments.
What component is vulnerable in CVE-2026-68871?
The vulnerability lies within the Yandex Lockbox secrets backend in the Apache Airflow Yandex provider.
Can CVE-2026-68871 lead to unauthorized data access?
Yes, CVE-2026-68871 can allow users from one team to access secrets belonging to another team, posing a risk of unauthorized data exposure.