Quick answers
- Is CVE-2026-76185 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-76185 being exploited in the wild.
- How severe is CVE-2026-76185?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Airflow prior to 3.4.0.
- Is there a fix for CVE-2026-76185?
- Yes: fixed in apache-airflow 3.4.0 or later. Until then: Deployments unable to upgrade can set `secrets.use_cache = False` to disable the vulnerable caching mechanism. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-76185 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-76185?
- Check whether you run Apache Airflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: apache-airflow 3.4.0 or later
Deployments unable to upgrade can set `secrets.use_cache = False` to disable the vulnerable caching mechanism.
Technical details
The SecretCache built keys by concatenating a prefix, an optional `_{team}_` segment, and a secret key using string concatenation, which is not injective when the team segment is optional. For example, team "analytics" with key "DB_PASSWORD" produces the same cache key as no team with key "_analytics_DB_PASSWORD". This collision allows reads, writes, and invalidations to resolve to the same cache slot, permitting cross-team secret disclosure or cache poisoning when both `core.multi_team = True` and `secrets.use_cache = True`.
Affected products
- Apache Airflow prior to 3.4.0
Timeline
- 2026-11-09: disclosed