cve.bz

CVE-2026-68871 apache apache-airflow-providers-apache-yandex

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in apache apache-airflow-providers-apache-yandex. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow-providers-yandex 4.5.1.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-68871 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-68871?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-68871?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-68871 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-68871

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-68871](https://cve.bz/cve/badge/CVE-2026-68871.svg)](https://cve.bz/cve/CVE-2026-68871)

HTML:

<a href="https://cve.bz/cve/CVE-2026-68871"><img src="https://cve.bz/cve/badge/CVE-2026-68871.svg" alt="CVE-2026-68871"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflow Yandex providerbefore 4.5.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qmrf-jrpr-rjx6PyPIapache-airflow-providers-yandex<4.5.14.5.1
PYSEC-2026-3715PyPIapache-airflow-providers-yandex<4.5.14.5.1

References

Check your stackJSON