Apache Airflow's secrets masker matched sensitive key names only in their snake_case form, so values stored under
Source GCVE Database
Not known to be exploited : upgrade to 3.0.0 soon.
Data as of 9 Nov 2026, 13:32 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 3.0.0, 3.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 and apache-airflow to 3.0.0; Apache Airflow and apache-airflow-core to 3.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflowapache-airflow | Affected
| Fixed in
|
| Apache Airflowapache-airflow-core | Affected
| Fixed in
|
PyPIapache-airflowpkg:pypi/apache-airflowOther threats | Affected
| Fixed in
|
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther 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
Upgrade Apache Airflow to version 3.4.0 or later, where the secrets masker correctly redacts sensitive keys regardless of naming convention. No other mitigation steps are indicated.
Description
Apache Airflow versions prior to 3.4.0 had a flaw in their secrets masker where sensitive keys were only matched in snake_case form. As a result, sensitive values stored under camelCase keys such as privateKey, connectionString, webhookUrl, or accessKey were not redacted in task logs, rendered templates, or API responses. This could allow unauthorized users with access to task logs or rendered templates to view sensitive credentials in cleartext. Upgrading to Apache Airflow 3.4.0 or later addresses this issue.