NVD / CVE Program· CNA GitHub_M

CVE-2026-30967: Parse Server OAuth2 authentication adapter account takeover via identity spoofing

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: parse-community parse-server 9.5.2-alpha.9.

Low priority for now. Upgrade to parse-community parse-server 9.5.2-alpha.9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.6 · v4.0—No exploit Fix available

Auth bypass

GHSA-fr88-w35c-r596

Published: Mar 10, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 29th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.6; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
parseplatform	parse-server	cpe:2.3:a:parseplatform:parse-server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

parseplatform parse-serverbefore 8.6.22
parseplatform parse-server9.0.0 and later · before 9.5.2
parseplatform parse-server9.5.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

parse-community parse-server
- >= 9.0.0 < 9.5.2-alpha.9, < 8.6.22affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
npm	parse-server	from 9.0.0-alpha.1 · before 9.5.2-alpha.9	9.5.2-alpha.9
npm	parse-server	before 8.6.22	8.6.22

Same product

parseplatform: all records

Other highest-scoring records for the same primary product.

CVE-2022-24760Command Injection in Parse server
55Plan
CVE-2022-39396Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser
51Plan
CVE-2026-30966Parse Server role escalation and CLP bypass via direct `_Join` table write
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-30962Mar 10, 2026 · Parse Server has a protected fields bypass via logical query operators
28Monitor
← EarlierCVE-2026-30965Mar 10, 2026 · Parse Server session token exfiltration via `redirectClassNameForKey` query parameter
39Monitor
Later →CVE-2026-30972Mar 10, 2026 · Parse Server has a rate limit bypass via batch request endpoint
27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
parse-community parse-server	9.5.2-alpha.9 · description	Vendor (CNA)
npm:parse-server	8.6.22	Package registry (OSV)
npm:parse-server	9.5.2-alpha.9	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-308633 days apartParse Server: JWT audience validation bypass in Google, Apple, and Facebook authentication adapters
37Monitor
CVE-2026-309490 days apartParse Server is missing audience validation in Keycloak authentication adapter
30Monitor
CVE-2026-3340914 days apartParse Server: Auth provider validation bypass on login via partial authData
28Monitor
CVE-2026-330428 days apartParse Server affected by empty authData bypassing credential requirement on signup
27Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-3353914 days apartParse Server: SQL injection via aggregate and distinct field names in PostgreSQL adapter
34Monitor
CVE-2025-6815084 days apartParse Server has Server-Side Request Forgery (SSRF) in Instagram OAuth Adapter
33Monitor
CVE-2026-322341 days apartParse Server has a SQL injection via query field name when using PostgreSQL
20Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records