Home

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.9. and 8.6.22, the OAuth2 authentication adapter, when configured without the useridField option, only verifies that a token is active via the provider's token introspection endpoint, but does not verify that the token belongs to the user identified by authData.id. An attacker with any valid OAuth2 token from the same provider can authenticate as any other user. This affects any Parse Server deployment that uses the generic OAuth2 authentication adapter (configured with oauth2: true) without setting the useridField option. This vulnerability is fixed in 9.5.2-alpha.9. and 8.6.22.

PUBLISHED Reserved 2026-03-07 | Published 2026-03-10 | Updated 2026-03-11 | Assigner GitHub_M




HIGH: 7.6CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-287: Improper Authentication

Product status

>= 9.0.0 < 9.5.2-alpha.9
affected

< 8.6.22
affected

References

github.com/...server/security/advisories/GHSA-fr88-w35c-r596

github.com/parse-community/parse-server/releases/tag/8.6.22

github.com/...munity/parse-server/releases/tag/9.5.2-alpha.9

cve.org (CVE-2026-30967)

nvd.nist.gov (CVE-2026-30967)

Download JSON