Vulnerability Description
When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+ Users are recommended to upgrade to version 3.2.0, which fixes this issue.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Apache | Airflow | >= 3.0.0, < 3.2.0 |
Related Weaknesses (CWE)
References
- https://github.com/apache/airflow/pull/56633Issue Tracking
- https://github.com/apache/airflow/pull/61339Issue Tracking
- https://lists.apache.org/thread/ovn8mpd8zkc604hojt7x3wsw3kc60x98Mailing ListVendor Advisory
- http://www.openwall.com/lists/oss-security/2026/04/09/16Mailing ListThird Party Advisory
FAQ
What is CVE-2025-57735?
CVE-2025-57735 is a vulnerability with a CVSS score of 9.1 (CRITICAL). When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanis...
How severe is CVE-2025-57735?
CVE-2025-57735 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2025-57735?
Check the references section above for vendor advisories and patch information. Affected products include: Apache Airflow.