CVE-2026-33409
Parseplatform Parse-server authentication bypass
- Published24 Mar 2026
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.52 and 9.6.0-alpha.41, an authentication bypass vulnerability allows an attacker to log in as any user who has linked a third-party authentication provider, without knowing the user's credentials. The attacker only needs to know the user's provider ID to gain full access to their account, including a valid session token. This affects Parse Server deployments where the server option allowExpiredAuthDataToken is set to true. The default value is false. This issue has been patched in versions 8.6.52 and 9.6.0-alpha.41.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- https://github.com/parse-community/parse-server/commit/8d7df5639c4a35768fe8b78b4580b30e8a74721c
- https://github.com/parse-community/parse-server/commit/98f4ba5bcf2c199bfe6225f672e8edcd08ba732d
- https://github.com/parse-community/parse-server/pull/10246
- https://github.com/parse-community/parse-server/pull/10247
- https://github.com/parse-community/parse-server/security/advisories/GHSA-pfj7-wv7c-22pr
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-33409 being actively exploited?
CVE-2026-33409 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.56%.
How severe is CVE-2026-33409?
CVE-2026-33409 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.56% probability of exploitation.
Which products are affected by CVE-2026-33409?
Affected products include Parseplatform Parse-server.
How do I fix CVE-2026-33409?
Upgrade affected software to a fixed version, for example Parseplatform Parse-server 9.6.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-33409 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.