CVE-2026-68871

Apache Airflow Yandex provider: yandex Lockbox backend: team-scope guard bypass resolves another team's Connection or Variable

Published Aug 10, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Yandex Lockbox secrets backend in Apache Airflow's Yandex provider allows a user in a multi‑team deployment to resolve a secret that belongs to another team. When the lookup for a team‑scoped Connection or Variable fails, the backend falls back to a team‑agnostic lookup that can interpret an identifier as a team namespace. This bypass of the team‑scope guard enables access to another team’s credentials through a simple lookup of the target team’s namespace.

Affected Systems

Apache Airflow in the Yandex provider component, specifically when the Yandex Lockbox backend is enabled and multi‑team mode is active. The CVE report does not specify affected product versions, so any installation using the Yandex provider with multi‑team mode may be vulnerable.

Risk and Exploitability

The vulnerability is an Authorization Bypass Through User‑Controlled Key (CWE‑639). It does not require uncommon configuration – merely enabling multi‑team mode and using the Yandex Lockbox backend. The CVSS score is 6.5 and the EPSS score is < 1%, indicating a moderate severity with a low exploitation probability. The KEV status is not listed, indicating no public reports of exploitation yet. Because secrets are disclosed, the potential impact is high for confidentiality and may allow lateral movement in a multi‑team Airflow environment.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to apache‑airflow‑providers‑yandex 4.5.1 or later, which blocks the team‑agnostic fallback for identifiers that name a team namespace.
  • If an upgrade cannot be performed immediately, consider disabling multi‑team mode or removing the Yandex Lockbox backend from the configuration until the patch is applied.
  • Review existing team‑scoped secrets to ensure that only the appropriate teams have access, and audit Airflow’s access controls to limit secret exposure across teams.

Generated by OpenCVE AI on August 13, 2026 at 03:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-qmrf-jrpr-rjx6 Apache Airflow Yandex Lockbox backend allows cross-team secret disclosure
History
Type Values Removed Values Added
First Time appeared Apache apache-airflow-providers-apache-yandex
CPEs cpe:2.3:a:apache:apache-airflow-providers-apache-yandex:*:*:*:*:*:*:*:*
Vendors & Products Apache apache-airflow-providers-apache-yandex
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache airflow Yandex Provider
Vendors & Products Apache
Apache airflow Yandex Provider
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
Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 16, 2026, 2:56 PM
Reserved
Jul 31, 2026, 7:39 PM
Status
Analyzed
Published
Aug 10, 2026, 7:17 PM
Modified
Oct 24, 2026, 4:10 PM