CVE-2026-86465: Apache Airflow Akeyless provider: Akeyless secrets backend: team-scope guard bypass via user-controlled key
Apache Airflow Akeyless provider before 0.3.1 lets DAG authors bypass team-scope guards and read other teams' secrets.
30
Vulnerability1 · 1 read
CVE-2026-86465
Team-scope authorization bypass in Apache Airflow Akeyless secrets backend
- CVSS 3.1
- 6.5 medium
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
CVE-2026-86465 is an authorization bypass (CWE-639) in the Akeyless secrets backend of the Apache Airflow Akeyless provider, where a team-scope guard can be bypassed with a user-controlled key. A Dag author scoped to one team can supply a Variable key containing a path separator, which is concatenated unvalidated into the lookup path after the team-scoped lookup misses, causing the backend to resolve a secret belonging to a different team; the Execution API Variables route accepts path-shaped keys, so this is reachable from ordinary Dag code. An attacker gains read access to secrets outside their authorized team scope in multi-team deployments. Only multi-team deployments using the Akeyless secrets backend are affected; single-team deployments have no cross-team boundary to cross and are not affected. No public proof-of-concept or in-the-wild exploitation is known, the issue is not in CISA KEV, and no CVSS score has been assigned yet.
What to do: Upgrade apache-airflow-providers-akeyless to version 0.3.1 or later, prioritizing multi-team deployments that use the Akeyless secrets backend; single-team deployments are not affected. Review existing Variable keys in Dag code for path-shaped values and limit which Dag authors can set Variables where possible. Organizations using the related Azure Key Vault, Yandex Lockbox, or Amazon secrets backends should also apply the fixes for CVE-2026-68870, CVE-2026-68871, and CVE-2026-68872.
| Product | Affected |
|---|---|
| apache-airflow-providers-akeyless (Akeyless secrets backend for Apache Airflow) | all versions prior to 0.3.1 |
Estimated exposure
moderate≈1,000–5,000 Airflow deployments at most (the small fraction of Airflow's large install base that uses the Akeyless backend in a multi-team, team-scoped… — Airflow is deployed by tens of thousands of organizations, but exploitation requires the relatively uncommon Akeyless secrets backend plus a multi-team deployment with team-scoped Dag authors, which together likely narrow the affected base…
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
Apache Airflow Akeyless provider: the Akeyless secrets backend's team-scope guard can be bypassed with a user-controlled key. In a multi-team deployment, a Dag author scoped to one team can supply a Variable key containing a path separator that causes the backend to resolve a secret belonging to a different team, because the lookup path is concatenated from an unvalidated key after the team-scoped lookup misses. The Execution API Variables route accepts a path-shaped key, so this is reachable from ordinary Dag code. Affects multi-team deployments using the Akeyless secrets backend. Single-team deployments are not affected, as there is no cross-team boundary to cross. This is the same class as CVE-2026-68870, CVE-2026-68871 and CVE-2026-68872 in the Azure Key Vault, Yandex Lockbox and Amazon secrets backends. Users of apache-airflow-providers-akeyless are recommended to upgrade to version 0.3.1 or later, which fixes the issue.
- Vendors
- apache
- Products
- apache-airflow-providers-akeyless
- Weakness
- CWE-639
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N