CVE-2025-57735: Apache Airflow JWT Token Vulnerability Post-Logout
Summary
CVE-2025-57735: Apache Airflow: JWT token still valid after logout. 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-2025-57735 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
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 and visualize these workflows. However, it has been found that the JWT (JSON Web Token) used for authentication remains valid even after a user logs out, posing a security risk.
Vulnerability Detail
The vulnerability arises from the failure to invalidate the JWT token upon user logout. This oversight means that if an attacker intercepts the token before logout, they can continue to use it to gain unauthorized access to the system. The issue was identified in versions prior to 3.2.0 of Apache Airflow, where the logout mechanism did not properly handle token invalidation, leading to potential misuse of valid tokens.
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 workaround, users can manually revoke JWT tokens by implementing a custom logout function that invalidates the token on the server side. However, this is not a permanent solution and upgrading is strongly recommended.
Conclusion
The vulnerability identified as CVE-2025-57735 in Apache Airflow poses a significant security risk due to the failure to invalidate JWT tokens upon user logout. Users are strongly advised to upgrade to version 3.2.0 or later to mitigate this risk effectively. Implementing workarounds may provide temporary relief, but upgrading is the best long-term solution.
See every vulnerability recorded for apache-airflow →
FAQ
The CVSS score for this vulnerability is 9.1, indicating a high level of severity.
Versions prior to 3.2.0 of Apache Airflow are affected by this vulnerability.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If an immediate upgrade is not possible, consider implementing a custom logout function to invalidate JWT tokens manually as a temporary workaround.
More information can be found in the official Apache Airflow documentation and security advisories related to CVE-2025-57735.
References
Related vulnerabilities
Recent vulnerabilities recorded for apache-airflow.
