Apache Airflow: Insertion of Sensitive Information into Log File
CVE-2026-31987 is a high-severity insertion of sensitive information into log file vulnerability in Apache Airflow from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 3.2.0 as the first without the flaw, so updating Apache Airflow to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.75% chance of exploitation within 30 days, higher than 56% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Apache Airflow to 3.2.0 or a later version.
- Update Airflow to 3.2.0 or a later version.
- Read the advisory on lists.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache Airflow | 3.0.0 up to, but not including, 3.2.0 | 3.2.0 |
| Apache | Airflow | 3.0.0 up to, but not including, 3.2.0 | 3.2.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CISA (ADP).
Official description
JWT Tokens used by tasks were exposed in logs. This could allow UI users to act as Dag Authors. Users are advised to upgrade to Airflow version that contains fix. Users are recommended to upgrade to version 3.2.0, which fixes this issue.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How developers prevent this class of flaw
- Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Remove debug log files before deploying the application into production.
- Protect log files against unauthorized read/write.
More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- github.com/apache/airflow/pull/62964Issue Tracking, Third Party Advisory
Third-party and government advisories
- openwall.com/lists/oss-security/2026/04/16/7Mailing List, Third Party Advisory
Other references
- github.com/apache/airflow/issues/62428Issue Tracking
- github.com/apache/airflow/issues/62773Issue Tracking
Other vulnerabilities in Apache Airflow
- 8.8 High severity
- 8.8 High severity
- 7.3 High severity
- 9.8 Critical severity
- 8.2 High severity
- 7.5 High severity
Recent Insertion of Sensitive Information into Log File vulnerabilities
- 7.2 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.3 High severity
Spotted an error? Tell us.