How severe is CVE-2025-64386?

CVE-2025-64386 has a CVSS 4.0 base score of 7.7, rated high severity.

Is CVE-2025-64386 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-64386?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-64386 have an EU (EUVD) identifier?

Yes. CVE-2025-64386 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-37348.

When was CVE-2025-64386 published?

CVE-2025-64386 was published on 2025-10-31 and last updated on 2026-06-17.

CVE-2025-64386

CVE-2025-64386 is a high-severity vulnerability with a CVSS 4.0 base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-613.

Key facts

Severity: High (CVSS 4.0 base score 7.7)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-37348
Weakness: CWE-613
Published: 2025-10-31
Last modified: 2026-06-17

Description

The equipment grants a JWT token for each connection in the timeline, but during an active valid session, a hijacking of the token can be done. This will allow an attacker with the token modify parameters of security, access or even steal the session without the legitimate and active session detecting it. The web server allows the attacker to reuse an old session JWT token while the legitimate session is active.

Frequently asked questions

What is CVE-2025-64386?: The equipment grants a JWT token for each connection in the timeline, but during an active valid session, a hijacking of the token can be done. This will allow an attacker with the token modify parameters of security, access or even steal the session without the legitimate and active session detecting it. The web server allows the attacker to reuse an old session JWT token while the legitimate session is active.
How severe is CVE-2025-64386?: CVE-2025-64386 has a CVSS 4.0 base score of 7.7, rated high severity.
Is CVE-2025-64386 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-64386?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-64386 have an EU (EUVD) identifier?: Yes. CVE-2025-64386 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-37348.
When was CVE-2025-64386 published?: CVE-2025-64386 was published on 2025-10-31 and last updated on 2026-06-17.

References

Other CWE-613 (Insufficient Session Expiration) vulnerabilities

CVE-2024-8888 — Critical (CVSS 10.0): An attacker with access to the network where CIRCUTOR Q-SMT is located in its firmware version 1.0.4, could steal the…
CVE-2026-46455 — Critical (CVSS 9.8): Insufficient Session Expiration vulnerability in Apache Camel Keycloak Component. The camel-keycloak security helper…
CVE-2026-21622 — Critical (CVSS 9.8): Insufficient Session Expiration vulnerability in hexpm hexpm/hexpm ('Elixir.Hexpm.Accounts.PasswordReset' module)…
CVE-2025-59786 — Critical (CVSS 9.8): 2N Access Commander version 3.4.2 and prior improperly invalidates session tokens, allowing multiple session cookies to…
CVE-2026-26342 — Critical (CVSS 9.8): Tattile Smart+, Vega, and Basic device families firmware versions 1.181.5 and prior implement an authentication token…
CVE-2026-1435 — Critical (CVSS 9.8): Not properly invalidated session vulnerability in Graylog Web Interface, version 2.2.3, due to incorrect management of…

Browse all CWE-613 (Insufficient Session Expiration) vulnerabilities →