CVE-2026-30965: Parse Server vulnerable to session token exfiltration via `redirectClassNameForKey` query parameter
Impact 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.
Published Mar 11, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0-alpha.1, < 9.5.2-alpha.8
- Fixed in
- 9.5.2-alpha.8
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.21
- Fixed in
- 8.6.21
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Patches
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.
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
Credited to theinfosecguy, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-6r2j-cxgf-495f
- https://nvd.nist.gov/vuln/detail/CVE-2026-30965
- https://github.com/parse-community/parse-server/releases/tag/8.6.21
- https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.8
- https://github.com/advisories/GHSA-6r2j-cxgf-495f
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-34532
parse-server has cloud function validator bypass via prototype chain traversal
critical9.1Mar 31, 2026CVE-2026-32242
Parse Server's OAuth2 adapter shares mutable state across providers via singleton instance
critical9.1Mar 12, 2026CVE-2026-32248
Parse Server: Account takeover via operator injection in authentication data identifier
critical9.3Mar 12, 2026CVE-2026-30966
Parse Server has role escalation and CLP bypass via direct `_Join` table write
critical10.0Mar 11, 2026CVE-2026-31856
Parse Server vulnerable to SQL injection via `Increment` operation on nested object field in PostgreSQL
critical9.3Mar 11, 2026CVE-2026-31871
Parse Server vulnerable to SQL Injection via dot-notation sub-key name in `Increment` operation on PostgreSQL
critical9.3Mar 11, 2026
