CVE-2026-31987: Apache Airflow JWT Token Exposure in Logs
Summary
CVE-2026-31987: Apache Airflow: JWT token appearing in logs. Affects apache-airflow versions >= 3.0.0, < 3.2.0. Fixed in 3.2.0. How to fix ↓
Also tracked for
- airflow · Bitnami
The same CVE-2026-31987 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Apache Airflow is an open-source platform designed to programmatically author, schedule, and monitor workflows. It allows users to define workflows as Directed Acyclic Graphs (DAGs) and provides a rich user interface to manage these workflows. However, it has been identified that JWT tokens used by tasks can be inadvertently logged, leading to potential security risks.
Vulnerability Detail
The vulnerability arises from the exposure of JWT tokens in the logs generated by Apache Airflow. This exposure can allow unauthorized users with access to the UI to impersonate DAG authors, potentially leading to unauthorized actions within the workflows. The issue is particularly concerning as it can compromise the integrity and confidentiality of the workflows managed by Airflow.
How To Fix
Latest published version: 3.3.2 as of 22 Oct 2026
pip install --upgrade "apache-airflow==3.3.2"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.2.0
This is the first release that contains the fix.
pip install --upgrade "apache-airflow==3.2.0"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary measure, users can limit access to the logs or implement logging configurations that do not include sensitive information such as JWT tokens. However, upgrading to the patched version is strongly recommended for a permanent fix.
Conclusion
In summary, the vulnerability identified as CVE-2026-31987 in Apache Airflow poses a significant risk due to the exposure of JWT tokens in logs. Users are strongly advised to upgrade to version 3.2.0 or later to mitigate this risk and ensure the security of their workflows.
See every vulnerability recorded for apache-airflow →
FAQ
The vulnerability involves the exposure of JWT tokens in Apache Airflow logs, which can allow unauthorized users to act as DAG authors.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If exploited, this vulnerability can lead to unauthorized access and manipulation of workflows, compromising the security of the entire system.
Yes, upgrading to Apache Airflow version 3.2.0 or later will fix this vulnerability.
The CVSS score of this vulnerability is 7.5, indicating a high severity level.
References
Related vulnerabilities
Recent vulnerabilities recorded for apache-airflow.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
