CVE-2026-32248

Workarounds

There is no known workaround.

References

• GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-5fw2-8jcv-xh87
• Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.12
• Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.38

An unauthenticated attacker can take over any user account that was created with an authentication provider that does not validate the format of the user identifier (e.g. anonymous authentication). By sending a crafted login request, the attacker can cause the server to perform a pattern-matching query instead of an exact-match lookup, allowing the attacker to match an existing user and obtain a valid session token for that user's account. Both MongoDB and PostgreSQL database backends are affected. Any Parse Server deployment that allows anonymous authentication (enabled by default) is vulnerable.

Kodem intelligence

The fix enforces that the user identifier in authentication data is a string before using it in a database query. Non-string values are rejected with a validation error.

1. What is CVE-2026-32248? CVE-2026-32248 is a critical-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.6.0-alpha.12. It is fixed in 9.6.0-alpha.12, 8.6.38.
2. Which versions of parse-server are affected by CVE-2026-32248? parse-server (npm) versions >= 9.0.0, < 9.6.0-alpha.12 is affected.
3. Is there a fix for CVE-2026-32248? Yes. CVE-2026-32248 is fixed in 9.6.0-alpha.12, 8.6.38. Upgrade to this version or later.
4. Is CVE-2026-32248 exploitable, and should I be worried? Whether CVE-2026-32248 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-2026-32248 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-2026-32248?
   • Upgrade parse-server to 9.6.0-alpha.12 or later
   • Upgrade parse-server to 8.6.38 or later

Other vulnerabilities in parse-server