CVE-2026-30965

Workarounds

Set restrictive Class-Level Permissions to prevent clients from creating new fields on classes, specifically by disabling addField for public access and unauthenticated users. Note that this limits client functionality and does not fully eliminate the risk if a relation field pointing to a protected class already exists in the schema.

References

• GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-6r2j-cxgf-495f
• Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.8
• Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.21

A vulnerability in Parse Server's query handling allows an authenticated or unauthenticated attacker to exfiltrate session tokens of other users by exploiting the redirectClassNameForKey query parameter. Exfiltrated session tokens can be used to take over user accounts.

The vulnerability requires the attacker to be able to create or update an object with a new relation field, which depends on the Class-Level Permissions of at least one class.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Kodem intelligence

The fix applies the same security checks that normally protect class access after the query redirect, ensuring that queries redirected via redirectClassNameForKey are subject to the same restrictions as direct queries to the target class.

1. What is CVE-2026-30965? CVE-2026-30965 is a critical-severity incorrect authorization vulnerability in parse-server (npm), affecting versions >= 9.0.0-alpha.1, < 9.5.2-alpha.8. It is fixed in 9.5.2-alpha.8, 8.6.21. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. Which versions of parse-server are affected by CVE-2026-30965? parse-server (npm) versions >= 9.0.0-alpha.1, < 9.5.2-alpha.8 is affected.
3. Is there a fix for CVE-2026-30965? Yes. CVE-2026-30965 is fixed in 9.5.2-alpha.8, 8.6.21. Upgrade to this version or later.
4. Is CVE-2026-30965 exploitable, and should I be worried? Whether CVE-2026-30965 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-30965 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-30965?
   • Upgrade parse-server to 9.5.2-alpha.8 or later
   • Upgrade parse-server to 8.6.21 or later

Other vulnerabilities in parse-server