https://seclists.org/oss-sec/2026/q3/922: CVE-2026-97636: Apache Airflow HashiCorp provider: HashiCorp Vault sects backend: team-scope guard bypass via user-controlled key

Q: Which deployments are exposed to cross-team secret access?

Multi-team Apache Airflow deployments that use the HashiCorp Vault secrets backend are affected when running provider versions 4.6.0 before 4.8.0. Single-team deployments are not affected because they have no team boundary to bypass.

Q: What does an attacker need to exploit this issue?

A DAG author scoped to one team must be able to supply a Variable key through ordinary DAG code. Exploitation relies on using a path-shaped key containing a path separator, causing the team-scoped lookup to miss and fall back to a team-agnostic Vault path.

Q: How should affected installations remediate the issue?

Upgrade apache-airflow-providers-hashicorp to version 4.8.0 or later. The provided data does not specify an alternative mitigation for installations that cannot yet upgrade.

Published Sep 24, 2026

Updated

Affected Software

1 affected component

pypi/apache-airflow-providers-hashicorp>=4.6.0<4.8.0

Frequently Asked Questions

Which deployments are exposed to cross-team secret access?

Multi-team Apache Airflow deployments that use the HashiCorp Vault secrets backend are affected when running provider versions 4.6.0 before 4.8.0. Single-team deployments are not affected because they have no team boundary to bypass.

What does an attacker need to exploit this issue?

A DAG author scoped to one team must be able to supply a Variable key through ordinary DAG code. Exploitation relies on using a path-shaped key containing a path separator, causing the team-scoped lookup to miss and fall back to a team-agnostic Vault path.

How should affected installations remediate the issue?

Upgrade apache-airflow-providers-hashicorp to version 4.8.0 or later. The provided data does not specify an alternative mitigation for installations that cannot yet upgrade.