CVE-2026-33421: 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 versions 8.6.53 and 9.6.0-alpha.42, Parse Server's LiveQuery WebSocket interface does not enforce Class-Level Permission (CLP) pointer permissions (readUserFields and pointerFields). Any authenticated user can subscribe to LiveQuery events and receive real-time updates for all objects in classes protected by pointer permissions, regardless of whether the pointer fields on those objects point to the subscribing user. This bypasses the intended read access control, allowing unauthorized access to potentially sensitive data that is correctly restricted via the REST API. This issue has been patched in versions 8.6.53 and 9.6.0-alpha.42.
AI Analysis
Technical Summary
Parse Server is an open-source backend platform that supports real-time data synchronization via its LiveQuery WebSocket interface. In affected versions prior to 8.6.53 and between 9.0.0 and 9.6.0-alpha.42, the LiveQuery interface does not correctly enforce Class-Level Permission (CLP) pointer permissions, specifically the readUserFields and pointerFields restrictions. These permissions are designed to restrict access to objects based on pointer fields that reference authorized users. However, due to this incorrect authorization, any authenticated user can subscribe to LiveQuery events and receive updates for all objects in classes that should be protected by pointer permissions, regardless of whether the pointer fields on those objects point to the subscribing user. This results in a bypass of intended access controls that are otherwise enforced by the REST API, exposing potentially sensitive data in real time. The vulnerability is classified under CWE-863 (Incorrect Authorization) and has a CVSS 4.0 base score of 7.1, indicating high severity. Exploitation requires only authentication, no user interaction, and can be performed remotely over the network. The issue was publicly disclosed on March 24, 2026, and patches are available in parse-server versions 8.6.53 and 9.6.0-alpha.42.
Potential Impact
This vulnerability can lead to unauthorized disclosure of sensitive data in real time, undermining confidentiality guarantees of applications using parse-server's LiveQuery feature. Attackers with valid credentials can bypass pointer-based access controls and subscribe to data streams they should not access, potentially exposing user information, business data, or other protected content. This can result in privacy violations, regulatory non-compliance, reputational damage, and potential exploitation of exposed data for further attacks. Since LiveQuery is often used for real-time updates in mobile and web applications, the scope of affected systems can be broad, impacting any organization relying on parse-server for backend services. The ease of exploitation (requiring only authentication and no user interaction) increases the risk, especially in environments with weak credential management or insider threats.
Mitigation Recommendations
Organizations should immediately upgrade parse-server to version 8.6.53 or later, or 9.6.0-alpha.42 or later, where the vulnerability is patched. Until upgrades can be applied, administrators should consider disabling the LiveQuery WebSocket interface if real-time updates are not critical, or implement additional application-layer access controls to restrict subscriptions based on user identity. Monitoring and logging WebSocket subscription requests can help detect anomalous subscription patterns indicative of exploitation attempts. Additionally, enforcing strong authentication mechanisms, such as multi-factor authentication, can reduce the risk of unauthorized access. Regularly auditing class-level permissions and pointer field configurations is recommended to ensure they are correctly set. Finally, developers should review their use of LiveQuery to minimize exposure of sensitive data and consider alternative real-time data delivery mechanisms if necessary.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Japan, South Korea, India, Brazil
CVE-2026-33421: 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 versions 8.6.53 and 9.6.0-alpha.42, Parse Server's LiveQuery WebSocket interface does not enforce Class-Level Permission (CLP) pointer permissions (readUserFields and pointerFields). Any authenticated user can subscribe to LiveQuery events and receive real-time updates for all objects in classes protected by pointer permissions, regardless of whether the pointer fields on those objects point to the subscribing user. This bypasses the intended read access control, allowing unauthorized access to potentially sensitive data that is correctly restricted via the REST API. This issue has been patched in versions 8.6.53 and 9.6.0-alpha.42.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Parse Server is an open-source backend platform that supports real-time data synchronization via its LiveQuery WebSocket interface. In affected versions prior to 8.6.53 and between 9.0.0 and 9.6.0-alpha.42, the LiveQuery interface does not correctly enforce Class-Level Permission (CLP) pointer permissions, specifically the readUserFields and pointerFields restrictions. These permissions are designed to restrict access to objects based on pointer fields that reference authorized users. However, due to this incorrect authorization, any authenticated user can subscribe to LiveQuery events and receive updates for all objects in classes that should be protected by pointer permissions, regardless of whether the pointer fields on those objects point to the subscribing user. This results in a bypass of intended access controls that are otherwise enforced by the REST API, exposing potentially sensitive data in real time. The vulnerability is classified under CWE-863 (Incorrect Authorization) and has a CVSS 4.0 base score of 7.1, indicating high severity. Exploitation requires only authentication, no user interaction, and can be performed remotely over the network. The issue was publicly disclosed on March 24, 2026, and patches are available in parse-server versions 8.6.53 and 9.6.0-alpha.42.
Potential Impact
This vulnerability can lead to unauthorized disclosure of sensitive data in real time, undermining confidentiality guarantees of applications using parse-server's LiveQuery feature. Attackers with valid credentials can bypass pointer-based access controls and subscribe to data streams they should not access, potentially exposing user information, business data, or other protected content. This can result in privacy violations, regulatory non-compliance, reputational damage, and potential exploitation of exposed data for further attacks. Since LiveQuery is often used for real-time updates in mobile and web applications, the scope of affected systems can be broad, impacting any organization relying on parse-server for backend services. The ease of exploitation (requiring only authentication and no user interaction) increases the risk, especially in environments with weak credential management or insider threats.
Mitigation Recommendations
Organizations should immediately upgrade parse-server to version 8.6.53 or later, or 9.6.0-alpha.42 or later, where the vulnerability is patched. Until upgrades can be applied, administrators should consider disabling the LiveQuery WebSocket interface if real-time updates are not critical, or implement additional application-layer access controls to restrict subscriptions based on user identity. Monitoring and logging WebSocket subscription requests can help detect anomalous subscription patterns indicative of exploitation attempts. Additionally, enforcing strong authentication mechanisms, such as multi-factor authentication, can reduce the risk of unauthorized access. Regularly auditing class-level permissions and pointer field configurations is recommended to ensure they are correctly set. Finally, developers should review their use of LiveQuery to minimize exposure of sensitive data and consider alternative real-time data delivery mechanisms if necessary.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-19T18:45:22.432Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c2d884f4197a8e3b5f9652
Added to database: 3/24/2026, 6:31:32 PM
Last enriched: 3/24/2026, 6:47:51 PM
Last updated: 3/26/2026, 5:40:17 AM
Views: 7
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 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.