CVE-2026-76185: Apache Airflow Task SDK: Task SDK SecretCache: non-injective team cache key enables cross-team secret disclosure in multi-team mode

Q: Which deployments are exposed?

Only Apache Airflow deployments where both core.multi_team is set to True and secrets.use_cache is set to True are affected. Deployments without multi-team mode or with the secret cache disabled are not affected by this issue.

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

The attacker needs to be a DAG author in a multi-team deployment. They can craft a secret ID that collides with another team's cache key and use it to read that team's Variable or Connection value.

Q: What can be done if an upgrade cannot be applied immediately?

Set secrets.use_cache to False to disable the affected Task SDK secret cache. This removes the cache-key collision condition described for this vulnerability.

Q: What version fixes the issue?

Upgrade to apache-airflow 3.4.0 or later.

Published Nov 9, 2026

Updated

Apache Airflow's Task SDK secret cache built its keys from the team name and secret id with unescaped delimiters, so different (team, secret id) pairs could collide. In multi-team deployments a Dag author could read another team's Variable or Connection value by crafting a colliding secret id. Only deployments with both core.multiteam = True and secrets.usecache = True are affected.

Users are advised to upgrade to apache-airflow 3.4.0 or later. Deployments that cannot upgrade can set secrets.usecache = False.

Affected Software

1 affected component

Apache Airflow<3.4.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade apache-airflow to a version that resolves this vulnerability.
Fixed in 3.4.0
Configuration
Set secrets.use_cache = False if the deployment cannot upgrade
Apache Airflow secrets.use_cache = False

Event History

Nov 9, 2026

CVE Published

via MITRE·09:53 AM

Data Sourced

via MITRE·09:53 AM

DescriptionWeakness

Data Sourced

via NVD·10:17 AM

DescriptionWeakness

Frequently Asked Questions

Which deployments are exposed?

Only Apache Airflow deployments where both core.multi_team is set to True and secrets.use_cache is set to True are affected. Deployments without multi-team mode or with the secret cache disabled are not affected by this issue.

What access does an attacker need to exploit this?

The attacker needs to be a DAG author in a multi-team deployment. They can craft a secret ID that collides with another team's cache key and use it to read that team's Variable or Connection value.

What can be done if an upgrade cannot be applied immediately?

Set secrets.use_cache to False to disable the affected Task SDK secret cache. This removes the cache-key collision condition described for this vulnerability.

What version fixes the issue?

Upgrade to apache-airflow 3.4.0 or later.

CVE-2026-76185: Apache Airflow Task SDK: Task SDK SecretCache: non-injective team cache key enables cross-team secret disclosure in multi-team mode

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed?

What access does an attacker need to exploit this?

What can be done if an upgrade cannot be applied immediately?

What version fixes the issue?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed?

What access does an attacker need to exploit this?

What can be done if an upgrade cannot be applied immediately?

What version fixes the issue?