VulnerabilityPublished 31 Mar 2026

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

Affects parse-serverSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 9.7.0-alpha.18 or 8.6.70 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.7.0-alpha.18, 8.6.70

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade parse-server to 9.7.0-alpha.18 or 8.6.70; parse-community/parse-server to 8.6.70.

Affected software

Product	Affected	Fixed in
parse-communityparse-server	Affected >=9.0.0 <9.7.0-alpha.18	Fixed in 9.7.0-alpha.18
parse-communityparse-server	Affected <8.6.70	Fixed in 8.6.70
npmparse-community/parse-server`pkg:npm/parse-community/parse-server`Other threats	Affected <8.6.70	Fixed in 8.6.70

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade parse-server to version 8.6.70 or later, or 9.7.0-alpha.18 or later, where the vulnerability has been patched. Until upgrade is possible, organizations should consider disabling LiveQuery subscriptions or restricting their use to trusted users only. Review and tighten class-level permissions, especially the find permission, to limit the number of users who can perform queries. Implement additional application-layer validation and monitoring to detect unusual subscription patterns that may indicate exploitation attempts. Employ network segmentation and access controls to limit exposure of parse-server instances. Regularly audit logs for suspicious LiveQuery subscription activity. Educate developers and administrators about the risks of using array-like objects in query filters and ensure input validation is robust. Finally, maintain an incident response plan to quickly address any detected exploitation.

Description

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.

Impact

This vulnerability can lead to unauthorized disclosure of sensitive data fields that are intended to be protected by class-level protectedFields permissions. Attackers with only find permission can bypass these restrictions on LiveQuery subscriptions, potentially exposing confidential information such as personally identifiable information, credentials, or business-critical data. The binary oracle side-channel allows attackers to infer exact values of protected fields, which can facilitate further attacks such as privilege escalation, data exfiltration, or targeted social engineering. Organizations relying on parse-server for real-time data synchronization and using protectedFields to enforce data confidentiality are at risk. The impact is particularly significant for applications handling sensitive user data, financial information, or regulated data subject to compliance requirements. Although exploitation requires authenticated access, many applications allow user registration or have multiple users, increasing the attack surface. The vulnerability does not affect availability or integrity directly but compromises confidentiality, which can have severe reputational and regulatory consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 15:39 UTC

WeaknessesCWE-843

Technical details

References

Community reviews

Related threats