Apache Airflow's Task SDK secret cache built its keys from the team name and secret id with unescaped _ delimiters, so
Source GCVE Database
Not known to be exploited : upgrade to 1.4.0 soon.
Data as of 9 Nov 2026, 13:18 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.4.0
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade Apache Airflow Task SDK and apache-airflow-task-sdk to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflow Task SDKapache-airflow-task-sdk | Affected
| Fixed in
|
PyPIapache-airflow-task-sdkpkg:pypi/apache-airflow-task-sdkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to Apache Airflow 3.4.0 or later where this issue is fixed. If upgrading is not feasible, setting secrets.use_cache = False disables the vulnerable secret cache feature and mitigates the risk.
Description
Apache Airflow versions with multi-team deployments and secret cache enabled have a vulnerability where secret cache keys are constructed using unescaped underscore delimiters from team names and secret IDs. This can cause key collisions allowing a DAG author to access another team's Variable or Connection values. The issue affects deployments with both core.multi_team = True and secrets.use_cache = True. Upgrading to Apache Airflow 3.4.0 or later or disabling the secret cache mitigates the issue.