cve.bz

CVE-2026-34595 parseplatform parse-server: Type Confusion

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in parseplatform parse-server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.70, 9.7.0-alpha.16.

On this page
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.70 and 9.7.0-alpha.18, an authenticated user with find class-level permission can bypass the protectedFields class-level permission setting on LiveQuery subscriptions. By sending a subscription with a $or, $and, or $nor operator value as a plain object with numeric keys and a length property (an "array-like" object) instead of an array, the protected-field guard is bypassed. The subscription event firing acts as a binary oracle, allowing the attacker to infer whether a protected field matches a given test value. This issue has been patched in versions 8.6.70 and 9.7.0-alpha.18.

Severity

CVSS 4.0

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

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-03-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34595 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34595?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34595?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34595 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverbefore 8.6.70
parseplatform:parse-serverfrom 9.0.0 before 9.7.0
parseplatform:parse-server9.7.0:alpha1
parseplatform:parse-server9.7.0:alpha10
parseplatform:parse-server9.7.0:alpha11
parseplatform:parse-server9.7.0:alpha12
parseplatform:parse-server9.7.0:alpha13
parseplatform:parse-server9.7.0:alpha14
parseplatform:parse-server9.7.0:alpha15
parseplatform:parse-server9.7.0:alpha2
parseplatform:parse-server9.7.0:alpha3
parseplatform:parse-server9.7.0:alpha4
parseplatform:parse-server9.7.0:alpha5
parseplatform:parse-server9.7.0:alpha6
parseplatform:parse-server9.7.0:alpha7
parseplatform:parse-server9.7.0:alpha8
parseplatform:parse-server9.7.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mmg8-87c5-jrc2npmparse-server>=9.0.0 <9.7.0-alpha.169.7.0-alpha.16
GHSA-mmg8-87c5-jrc2npmparse-server<8.6.708.6.70

References

Check your stackJSON