GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow Task SDK: secret cache key collision exposes other teams' Variables and Connections

UnscoredCVE-2026-76185Control plane, storage & DevOpscurated

Impact

The Task SDK built secret cache keys by joining the team name and secret id with unescaped _ characters, so two different (team, secret id) pairs could produce the same key. In a multi-team deployment, a Dag author can pick a secret id that collides with another team's entry and read that team's Variable or Connection value. This breaks the isolation that multi-team mode exists to provide on a shared Airflow instance.

Who can reach it

A Dag author in one team of a multi-team deployment. Requires the ability to deploy Dag code. Only affects deployments with both core.multi_team = True and secrets.use_cache = True.

What to do

Upgrade to apache-airflow 3.4.0 or later and restart the Airflow components. If you cannot upgrade, set secrets.use_cache = False and restart. Deployments without multi-team mode or without the secrets cache are not affected.

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.