Answer in brief
CVE-2025-57735 records a Critical severity (CVSS 9.1) vulnerability in Apache Airflow: JWT token still valid after logout. The current sources do not mark it as known exploited. The current feed maps apache-airflow (pip), apache-airflow (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps apache-airflow (pip), apache-airflow (pypi). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| apache-airflowpip | >=3.0.0,<3.2.0 | 3.2.0 |
| apache-airflowpypi | >=3.0.0 <3.2.0 | 3.2.0 |
Published upstream
Apr 9, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Oct 26, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.