Is CVE-2026-34595 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34595 being exploited in the wild.

How severe is CVE-2026-34595?

Medium severity, with a CVSS score of 4.3, published 31 March 2026.

Which products and versions are affected?

parse-server (npm) SEMVER:introduced=9.0.0,fixed=9.7.0-alpha.16.

Is there a fix for CVE-2026-34595?

Yes. parse-server (npm): upgrade to 9.7.0-alpha.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34595 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-34595?

Check whether you run parse-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34595: Parse Community Parse Server type confusion in LiveQuery protectedFields

CVE-2026-34595 · Severity: medium · CVSS 4.3 · Published 2026-03-31

Parse Server is an open-source backend used to build and host applications. A security flaw in its real-time update feature (LiveQuery) allows logged-in users to bypass privacy settings that are supposed to hide specific sensitive data fields. By exploiting this, an attacker could potentially figure out the contents of private information they are not authorized to see.

Technologies: parse-server (npm). Vendors: npm.

Quick answers

Is CVE-2026-34595 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34595 being exploited in the wild.
How severe is CVE-2026-34595?: Medium severity, with a CVSS score of 4.3, published 31 March 2026.
Which products and versions are affected?: parse-server (npm) SEMVER:introduced=9.0.0,fixed=9.7.0-alpha.16.
Is there a fix for CVE-2026-34595?: Yes. parse-server (npm): upgrade to 9.7.0-alpha.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34595 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34595?: Check whether you run parse-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

parse-server (npm): upgrade to 9.7.0-alpha.16 or later
```
npm install parse-server@9.7.0-alpha.16
```

Technical details

A type confusion vulnerability (CWE-843) exists in Parse Server's LiveQuery implementation. Authenticated users with 'find' class-level permissions can bypass 'protectedFields' restrictions by submitting a subscription query where logical operators ($or, $and, or $nor) contain an 'array-like' object (a plain object with numeric keys and a length property) instead of a standard array. This bypasses the protected-field guard, allowing the subscription event to act as a binary oracle. Attackers can use this to systematically infer the values of protected fields. The issue is fixed in versions 8.6.70 and 9.7.0-alpha.18.

Affected products

Parse Community Parse Server < 8.6.70, >= 9.0.0 < 9.7.0-alpha.18

Identifiers

CVE-2026-34595
GHSA-mmg8-87c5-jrc2

Timeline

2026-03-29: advisory: GitHub Security Advisory GHSA-mmg8-87c5-jrc2 published
2026-03-29: patched: Fixes merged into release branches
2026-03-31: disclosed: CVE-2026-34595 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.