Most recent entries from all

BIT-parse-2026-33409 — Parse Server: Auth provider validation bypass on login via partial authData

2026-10-13T05:34:27.307165+00:00

Affected: Bitnami: parse

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, 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

EUVD-2026-277348

2026-10-13T05:34:27.307230+00:00

EUVD-2026-277348

fkie_cve-2026-33409

2026-10-13T05:34:27.307252+00:00

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.

GHSA-pfj7-wv7c-22pr — Parse Server has an auth provider validation bypass on login via partial authData

2026-10-13T05:34:27.307303+00:00

Affected: npm: parse-server

### 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.