CVE-2026-86468: Apache Airflow · Sensitive Data in Logs
Affects Apache AirflowSource CVE Database V5
Not known to be exploited : upgrade to 3.4.0 soon.
Data as of 9 Nov 2026, 10:05 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.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 8 Nov 2026.
What to do
Upgrade Apache Airflow and apache-airflow-core to 3.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflowapache-airflow-core | 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 this issue is fixed. Additionally, purge audit log entries created before the upgrade that contain cleartext secrets and rotate any secrets that may have been exposed in those logs to prevent misuse.
Description
Apache Airflow versions prior to 3.4.0 have a vulnerability where sensitive information such as secrets can be logged in cleartext in audit logs due to incomplete masking of CLI arguments. This affects certain command arguments like trailing --description on Variable commands, --conn-extra, and inline --password in keycloak-auth-manager commands. Users with read access to audit logs but without Variable or Connection access can retrieve these secrets via the event-log API. The issue is fixed in version 3.4.0.