PT-2026-26493 · Npm · Parse Server

Published 2026-03-19 · Updated 2026-03-19 · CVE-2026-33409

OSV

CVSS v4.0

7.0

High

AV:N/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Impact

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.

Patches

Auth providers are now always validated on login, regardless of the allowExpiredAuthDataToken setting. The option allowExpiredAuthDataToken has been deprecated and will be removed in a future major version.

Workarounds

Set allowExpiredAuthDataToken to false (the default) or remove the option from the server configuration.

Fix

Improper Authentication

Weakness Enumeration

CWE-287

Related Identifiers

CVE-2026-33409

GHSA-PFJ7-WV7C-22PR

Affected Products

Parse Server

References · 5

• https://osv.dev/vulnerability/GHSA-pfj7-wv7c-22pr · Vendor Advisory
• https://github.com/parse-community/parse-server · Note
• https://github.com/parse-community/parse-server/pull/10246 · Note
• https://github.com/parse-community/parse-server/security/advisories/GHSA-pfj7-wv7c-22pr · Note
• https://github.com/parse-community/parse-server/pull/10247 · Note