CVE-2026-30965: CWE-863: Incorrect Authorization in parse-community parse-server
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.8 and 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. This vulnerability is fixed in 9.5.2-alpha.8 and 8.6.21.
AI Analysis
Technical Summary
Parse Server is an open-source backend framework that runs on Node.js and is widely used for building mobile and web applications. CVE-2026-30965 is an incorrect authorization vulnerability (CWE-863) discovered in parse-server's query handling mechanism. The flaw arises from improper authorization checks on the redirectClassNameForKey query parameter, which can be manipulated by attackers to access session tokens belonging to other users. The vulnerability can be exploited by either authenticated or unauthenticated attackers who have the capability to create or update objects with new relation fields, a capability governed by Class-Level Permissions (CLPs) on at least one class in the database schema. By exploiting this, attackers can exfiltrate session tokens without needing any privileges or user interaction. These session tokens can then be used to impersonate users, effectively allowing account takeover. The vulnerability affects parse-server versions from 8.x up to but not including 8.6.21, and 9.0.0 up to but not including 9.5.2-alpha.8. The CVSS 4.0 score of 9.9 reflects the critical nature of this vulnerability, with network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild, the ease of exploitation and severity make this a high-risk issue. The vulnerability was publicly disclosed on March 10, 2026, and fixed in the indicated patched versions.
Potential Impact
The impact of CVE-2026-30965 is severe for organizations using affected versions of parse-server. Successful exploitation leads to session token exfiltration, enabling attackers to hijack user accounts and gain unauthorized access to sensitive data and application functionality. This compromises confidentiality and integrity of user data and can disrupt availability if attackers perform malicious actions under hijacked accounts. Organizations relying on parse-server for backend services, especially those handling sensitive user information or critical business processes, face risks of data breaches, fraud, and reputational damage. The vulnerability requires no privileges or user interaction, increasing the likelihood of automated or large-scale attacks. Given parse-server's use in mobile and web applications globally, the threat surface is broad, potentially impacting startups, enterprises, and service providers. Without timely patching, attackers could leverage this flaw to escalate privileges, bypass access controls, and perform lateral movement within affected environments.
Mitigation Recommendations
To mitigate CVE-2026-30965, organizations should immediately upgrade parse-server to versions 9.5.2-alpha.8 or later, or 8.6.21 or later, where the vulnerability is fixed. Until upgrades can be applied, restrict access to parse-server endpoints by implementing network-level controls such as IP whitelisting and firewall rules to limit exposure. Review and tighten Class-Level Permissions (CLPs) to minimize the ability of users or unauthenticated actors to create or update objects with relation fields. Implement monitoring and alerting for unusual query patterns involving redirectClassNameForKey parameters or unexpected object relation modifications. Employ session token management best practices, including short token lifetimes and revocation mechanisms, to reduce the window of opportunity for attackers. Conduct thorough security assessments and penetration testing focused on authorization controls in parse-server deployments. Finally, maintain an up-to-date inventory of parse-server instances and ensure all development and production environments are patched promptly.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Japan, Netherlands, Brazil, South Korea, Singapore
CVE-2026-30965: CWE-863: Incorrect Authorization in parse-community parse-server
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.8 and 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. This vulnerability is fixed in 9.5.2-alpha.8 and 8.6.21.
AI-Powered Analysis
Technical Analysis
Parse Server is an open-source backend framework that runs on Node.js and is widely used for building mobile and web applications. CVE-2026-30965 is an incorrect authorization vulnerability (CWE-863) discovered in parse-server's query handling mechanism. The flaw arises from improper authorization checks on the redirectClassNameForKey query parameter, which can be manipulated by attackers to access session tokens belonging to other users. The vulnerability can be exploited by either authenticated or unauthenticated attackers who have the capability to create or update objects with new relation fields, a capability governed by Class-Level Permissions (CLPs) on at least one class in the database schema. By exploiting this, attackers can exfiltrate session tokens without needing any privileges or user interaction. These session tokens can then be used to impersonate users, effectively allowing account takeover. The vulnerability affects parse-server versions from 8.x up to but not including 8.6.21, and 9.0.0 up to but not including 9.5.2-alpha.8. The CVSS 4.0 score of 9.9 reflects the critical nature of this vulnerability, with network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. Although no known exploits have been reported in the wild, the ease of exploitation and severity make this a high-risk issue. The vulnerability was publicly disclosed on March 10, 2026, and fixed in the indicated patched versions.
Potential Impact
The impact of CVE-2026-30965 is severe for organizations using affected versions of parse-server. Successful exploitation leads to session token exfiltration, enabling attackers to hijack user accounts and gain unauthorized access to sensitive data and application functionality. This compromises confidentiality and integrity of user data and can disrupt availability if attackers perform malicious actions under hijacked accounts. Organizations relying on parse-server for backend services, especially those handling sensitive user information or critical business processes, face risks of data breaches, fraud, and reputational damage. The vulnerability requires no privileges or user interaction, increasing the likelihood of automated or large-scale attacks. Given parse-server's use in mobile and web applications globally, the threat surface is broad, potentially impacting startups, enterprises, and service providers. Without timely patching, attackers could leverage this flaw to escalate privileges, bypass access controls, and perform lateral movement within affected environments.
Mitigation Recommendations
To mitigate CVE-2026-30965, organizations should immediately upgrade parse-server to versions 9.5.2-alpha.8 or later, or 8.6.21 or later, where the vulnerability is fixed. Until upgrades can be applied, restrict access to parse-server endpoints by implementing network-level controls such as IP whitelisting and firewall rules to limit exposure. Review and tighten Class-Level Permissions (CLPs) to minimize the ability of users or unauthenticated actors to create or update objects with relation fields. Implement monitoring and alerting for unusual query patterns involving redirectClassNameForKey parameters or unexpected object relation modifications. Employ session token management best practices, including short token lifetimes and revocation mechanisms, to reduce the window of opportunity for attackers. Conduct thorough security assessments and penetration testing focused on authorization controls in parse-server deployments. Finally, maintain an up-to-date inventory of parse-server instances and ensure all development and production environments are patched promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-07T17:53:48.815Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69b0864c2f860ef943bbb061
Added to database: 3/10/2026, 8:59:56 PM
Last enriched: 3/10/2026, 9:15:20 PM
Last updated: 3/13/2026, 10:19:44 AM
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.