How severe is CVE-2025-4643?

CVE-2025-4643 has a CVSS 4.0 base score of 6.3, rated medium severity.

Is CVE-2025-4643 being actively exploited?

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

How do I fix CVE-2025-4643?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

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

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

When was CVE-2025-4643 published?

CVE-2025-4643 was published on 2025-08-29 and last updated on 2026-06-17.

CVE-2025-4643

CVE-2025-4643 is a medium-severity vulnerability with a CVSS 4.0 base score of 6.3. 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: Medium (CVSS 4.0 base score 6.3)
EPSS exploit prediction: 0% (38th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-26180
Weakness: CWE-613
Published: 2025-08-29
Last modified: 2026-06-17

Description

Payload uses JSON Web Tokens (JWT) for authentication. After log out JWT is not invalidated, which allows an attacker who has stolen or intercepted token to freely reuse it until expiration date (which is by default set to 2 hours, but can be changed). This issue has been fixed in version 3.44.0 of Payload.

Frequently asked questions

What is CVE-2025-4643?: Payload uses JSON Web Tokens (JWT) for authentication. After log out JWT is not invalidated, which allows an attacker who has stolen or intercepted token to freely reuse it until expiration date (which is by default set to 2 hours, but can be changed). This issue has been fixed in version 3.44.0 of Payload.
How severe is CVE-2025-4643?: CVE-2025-4643 has a CVSS 4.0 base score of 6.3, rated medium severity.
Is CVE-2025-4643 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-4643?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-4643 have an EU (EUVD) identifier?: Yes. CVE-2025-4643 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-26180.
When was CVE-2025-4643 published?: CVE-2025-4643 was published on 2025-08-29 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 →