Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 11 Aug 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache airflow Yandex Provider |
|
| Vendors & Products |
Apache
Apache airflow Yandex Provider |
Mon, 10 Aug 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache Airflow Yandex provider: yandex Lockbox backend: team-scope guard bypass resolves another team's Connection or Variable | |
| Weaknesses | CWE-639 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-08-11T12:08:24.112Z
Reserved: 2026-07-31T19:39:38.817Z
Link: CVE-2026-68871
No data.
Status : Received
Published: 2026-08-10T19:17:30.463
Modified: 2026-08-10T19:17:30.463
Link: CVE-2026-68871
No data.
OpenCVE Enrichment
Updated: 2026-08-11T14:22:16Z