CVE-2026-33042
Authentication Bypass in Parse Server via Empty authData Object
Publication date: 2026-03-18
Last updated on: 2026-03-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | From 9.0.0 (inc) to 9.6.0 (exc) |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | 9.6.0 |
| parseplatform | parse-server | to 8.6.49 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-287 | When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Parse Server versions prior to 9.6.0-alpha.29 and 8.6.49. It allows a user to sign up without providing any credentials by sending an empty `authData` object. This bypasses the usual requirement for a username and password, enabling the creation of authenticated sessions without proper authentication, even if anonymous users are disabled.
The issue was fixed by treating empty or non-actionable `authData` the same as absent `authData` during credential validation for new user creation, thus enforcing the requirement for username and password when no valid authentication provider data is present.
As a workaround before the fix, developers could use a Cloud Code `beforeSave` trigger on the `_User` class to reject signups where `authData` is empty and no username or password is provided.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to create authenticated sessions without valid credentials. This means attackers could gain access to the system as authenticated users without providing a username or password.
Such unauthorized access could lead to potential misuse of the system, unauthorized data access, or manipulation of user accounts, compromising the security and integrity of the application.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Parse Server to version 9.6.0-alpha.29 or 8.6.49 or later, where the issue is fixed.
As a workaround, implement a Cloud Code beforeSave trigger on the _User class to reject signups where the authData object is empty and no username or password is provided.