CVE-2026-76185 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Apache Airflow's Task SDK builds secret cache keys by joining team name and secret id with unescaped underscores, so different pairs can produce the same key. A Dag author in a multi-team deployment can craft a colliding secret id and read another team's Variable or Connection value.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only deployments that enable both core.multi_team = True and secrets.use_cache = True are affected, and the risk comes from Dag authors in one team reading another team's secrets. Single-team deployments, or those with the secret cache disabled, can skip it.
Not affected if default-config, secrets-cache-disabled, single-team-deployment
Who cares apache-airflow, multi-team, secrets, self-hosted
core.multi_team is set to True in the Airflow configuration.secrets.use_cache is set to True in the Airflow configuration.airflow version and compare it to 3.4.0.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.multi_team = True and secrets.use_cache = True are affected.
Users are advised to upgrade to apache-airflow 3.4.0 or later. Deployments that cannot upgrade can set secrets.use_cache = False.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
3.4.0 or later.secrets.use_cache = False.