Summary
Workarounds
Add a beforeSave trigger on the _Session class to validate and reject or strip any user-supplied values for sessionToken, expiresAt, and createdWith.
Impact
An authenticated user can overwrite server-generated session fields (sessionToken, expiresAt, createdWith) when creating a session object via POST /classes/_Session. This allows bypassing the server's session expiration policy by setting an arbitrary far-future expiration date. It also allows setting a predictable session token value.
CVE-2026-32742 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.6.0-alpha.17, 8.6.42); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.
Remediation advice
The session creation endpoint now filters out server-generated fields from user-supplied data, preventing them from being overwritten.
Frequently Asked Questions
- What is CVE-2026-32742? CVE-2026-32742 is a medium-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.6.0-alpha.17. It is fixed in 9.6.0-alpha.17, 8.6.42.
- How severe is CVE-2026-32742? CVE-2026-32742 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of parse-server are affected by CVE-2026-32742? parse-server (npm) versions >= 9.0.0, < 9.6.0-alpha.17 is affected.
- Is there a fix for CVE-2026-32742? Yes. CVE-2026-32742 is fixed in 9.6.0-alpha.17, 8.6.42. Upgrade to this version or later.
- Is CVE-2026-32742 exploitable, and should I be worried? Whether CVE-2026-32742 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
- What actually determines whether CVE-2026-32742 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.
- How do I fix CVE-2026-32742?
- Upgrade
parse-serverto 9.6.0-alpha.17 or later - Upgrade
parse-serverto 8.6.42 or later
- Upgrade