CVE-2026-30967: parse-server · Improper Authentication
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 9.5.2-alpha.9 or 8.6.22 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.5.2-alpha.9, 8.6.22
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade parse-server to 9.5.2-alpha.9 or 8.6.22; parse-community/parse-server to 8.6.22.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-server | Affected
| Fixed in
|
| parse-communityparse-server | Affected
| Fixed in
|
npmparse-community/parse-serverpkg:npm/parse-community/parse-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade all parse-server deployments to version 9.5.2-alpha.9 or later, or 8.6.22 or later, where the vulnerability is fixed.
- If upgrading immediately is not possible, ensure that the OAuth2 authentication adapter is configured with the useridField option correctly set to enforce token ownership verification.
- Review OAuth2 token issuance and storage policies to minimize token leakage or misuse.
- Implement additional monitoring and anomaly detection for suspicious authentication activities, such as token reuse across different user accounts.
- Conduct thorough audits of user authentication logs to detect potential unauthorized access.
- Educate developers and administrators on secure OAuth2 configuration practices within parse-server.
- Consider implementing multi-factor authentication (MFA) to reduce risk from token compromise.
- Regularly review and update dependencies and third-party components to incorporate security patches promptly.
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.