Apache Airflow: JWT token still valid after logout
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-57735US | — | — | ||
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 impl… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2026/04/09/16WEB
- https://github.com/advisories/GHSA-c92r-g8j5-vhcxADVISORY
- https://github.com/apache/airflowPACKAGE
- https://github.com/apache/airflow/pull/56633WEB
- https://github.com/apache/airflow/pull/61339WEB
- https://lists.apache.org/thread/ovn8mpd8zkc604hojt7x3wsw3kc60x98WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-57735ADVISORY
- https://pypi.org/project/apache-airflowPACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan