CVE-2026-33323

Description

### 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. ### Patches 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. ### Workarounds There is no known workaround to prevent the information disclosure other than upgrading.

How to fix CVE-2026-33323

To remediate CVE-2026-33323, upgrade the affected package to a fixed version below.

• —upgrade to 8.6.51 or later
• —upgrade to 9.6.0-alpha.40 or later

Is CVE-2026-33323 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 8.6.51, >= 9.0.0, < 9.6.0
• >= 9.0.0, < 9.6.0-alpha.40

CVSS scores

References (7)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-33323
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/commit/967aa57732202009b2389ce9ecb3130d53d657e5
• WEBgithub.com/parse-community/parse-server/commit/fbda4cb0c5cbc8fad08a216823b6b64d4ae289c3