CVE-2025-4644

CVE-2025-4644 is a medium-severity security vulnerability in payload (npm), affecting versions < 3.44.0. It is fixed in 3.44.0.

Summary

A Session Fixation vulnerability existed in Payload's SQLite adapter due to identifier reuse during account creation. A malicious attacker could create a new account, save its JSON Web Token (JWT), and then delete the account, which did not invalidate the JWT. As a result, the next newly created user would receive the same identifier, allowing the attacker to reuse the JWT to authenticate and perform actions as that user.

This issue has been fixed in version 3.44.0 of Payload.

Impact

Affected versions

payload (< 3.44.0) @payloadcms/next (< 3.44.0) @payloadcms/graphql (< 3.44.0)

Security releases

payload → 3.44.0 (npm) @payloadcms/next → 3.44.0 (npm) @payloadcms/graphql → 3.44.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

payload to 3.44.0 or later; @payloadcms/next to 3.44.0 or later; @payloadcms/graphql to 3.44.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-4644? CVE-2025-4644 is a medium-severity security vulnerability in payload (npm), affecting versions < 3.44.0. It is fixed in 3.44.0.
  2. Which packages are affected by CVE-2025-4644?
    • payload (npm) (versions < 3.44.0)
    • @payloadcms/next (npm) (versions < 3.44.0)
    • @payloadcms/graphql (npm) (versions < 3.44.0)
  3. Is there a fix for CVE-2025-4644? Yes. CVE-2025-4644 is fixed in 3.44.0. Upgrade to this version or later.
  4. Is CVE-2025-4644 exploitable, and should I be worried? Whether CVE-2025-4644 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2025-4644 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2025-4644?
    • Upgrade payload to 3.44.0 or later
    • Upgrade @payloadcms/next to 3.44.0 or later
    • Upgrade @payloadcms/graphql to 3.44.0 or later

Other vulnerabilities in payload

CVE-2026-34749CVE-2026-34746CVE-2026-34747CVE-2026-27567CVE-2026-25574

Stop the waste.
Protect your environment with Kodem.