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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Apache Airflow
cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*
|
3.0.0
|
3.2.0
|
References 4
https://github.com/apache/airflow/pull/56633
security@apache.org
https://github.com/apache/airflow/pull/61339
security@apache.org
https://lists.apache.org/thread/ovn8mpd8zkc604hojt7x3wsw3kc60x98
security@apache.org
http://www.openwall.com/lists/oss-security/2026/04/09/16
af854a3a-2127-422b-91ae-364da2661108