GPU VulnDB

Database/Control plane, storage & DevOps

Airflow Akeyless provider: path-shaped Variable key bypasses the team-scope guard on secret lookup

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

Impact

After a team-scoped lookup misses, the Akeyless backend concatenates an unvalidated, user-controlled key into the lookup path, so a key containing a path separator resolves a secret owned by a different team. The Execution API Variables route accepts a path-shaped key, which makes this reachable from ordinary Dag code rather than needing UI or admin access - any Dag author in a multi-team deployment can read another team's credentials. Vendors tracked the same class separately for the Azure Key Vault, Yandex Lockbox and Amazon backends (CVE-2026-68870, CVE-2026-68871, CVE-2026-68872); they are distinct packages with distinct fixes. Single-team deployments are unaffected.

Who can reach it

A Dag author or authenticated caller scoped to one team in a multi-team Airflow deployment using the Akeyless secrets backend. Reachable from normal Dag code through the Execution API.

What to do

Upgrade apache-airflow-providers-akeyless to 0.3.1 or later and restart scheduler, triggerer and workers. Rotate Akeyless-held secrets that a foreign team 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.