Summary
Workarounds
There is no known workaround to prevent the information disclosure other than upgrading.
Impact
The Pages route and legacy PublicAPI route for resending email verification links return distinguishable responses depending on whether the provided username exists and has an unverified email. This allows an unauthenticated attacker to enumerate valid usernames by observing different redirect targets. The existing emailVerifySuccessOnInvalidEmail configuration option, which is enabled by default and protects the API route against this, did not apply to these routes.
CVE-2026-33323 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no 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.40, 8.6.51); 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 email verification resend routes now respect the emailVerifySuccessOnInvalidEmail option. When set to true (the default), both routes redirect to the success page regardless of the outcome, preventing user enumeration.
Frequently Asked Questions
- What is CVE-2026-33323? CVE-2026-33323 is a medium-severity security vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.6.0-alpha.40. It is fixed in 9.6.0-alpha.40, 8.6.51.
- How severe is CVE-2026-33323? CVE-2026-33323 has a CVSS score of 5.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-33323? parse-server (npm) versions >= 9.0.0, < 9.6.0-alpha.40 is affected.
- Is there a fix for CVE-2026-33323? Yes. CVE-2026-33323 is fixed in 9.6.0-alpha.40, 8.6.51. Upgrade to this version or later.
- Is CVE-2026-33323 exploitable, and should I be worried? Whether CVE-2026-33323 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-33323 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-33323?
- Upgrade
parse-serverto 9.6.0-alpha.40 or later - Upgrade
parse-serverto 8.6.51 or later
- Upgrade