cve.bz

CVE-2025-57735 apache airflow: Insufficient Session Expiration

9.1 criticalEPSS 0.7%Fix available

Critical (9.1) in apache airflow. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow 3.2.0.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-04-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-57735 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-57735?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-57735?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-57735 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-57735

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-57735](https://cve.bz/cve/badge/CVE-2025-57735.svg)](https://cve.bz/cve/CVE-2025-57735)

HTML:

<a href="https://cve.bz/cve/CVE-2025-57735"><img src="https://cve.bz/cve/badge/CVE-2025-57735.svg" alt="CVE-2025-57735"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflowfrom 3.0.0 before 3.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c92r-g8j5-vhcxPyPIapache-airflow>=3.0.0 <3.2.03.2.0
PYSEC-2026-269PyPIapache-airflow>=3.0.0 <3.2.03.2.0

References

Check your stackJSON