GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow Yandex provider (Lockbox secrets backend, team-scope lookup): When the team-scoped lookup for a

CVSS 6.5CVE-2026-68871Control plane, storage & DevOpscurated

Impact

When the team-scoped lookup for a Connection or Variable id misses, the Lockbox backend retries the id against the team-agnostic path. In a multi-team deployment, a caller in one team can craft an id that names another team's namespace and retrieve that team's secret in full. Those secrets are typically the credentials pipelines use to reach object storage, registries and cluster APIs, so a cross-team read here is a cross-tenant credential handover on whatever the other team's jobs can touch. No unusual configuration is needed beyond multi-team mode plus this backend.

Who can reach it

Any authenticated Airflow user or Dag author scoped to one team in a multi-team deployment using the Yandex Lockbox secrets backend. Single-team deployments have no boundary to cross.

What to do

Upgrade apache-airflow-providers-yandex to 4.5.1 or later and restart the scheduler, triggerer and workers so the new provider is loaded; no node drain needed. Rotate any secret that a team other than its owner could have resolved.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.