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.
References
| Link | Resource |
|---|---|
| https://github.com/apache/airflow/pull/70877 | Issue Tracking Patch |
| https://lists.apache.org/thread/jlj9tv085txk4t0j029mvh43mz89o63c | Mailing List Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2026/08/10/5 | Mailing List Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-08-10 19:17
Updated : 2026-09-16 15:17
NVD link : CVE-2026-68871
Mitre link : CVE-2026-68871
CVE.ORG link : CVE-2026-68871
JSON object : View
Products Affected
apache
- apache-airflow-providers-apache-yandex
CWE
CWE-639
Authorization Bypass Through User-Controlled Key
