Skip to content
Connect AISign inSign up free
CVE-2026-343638.2HighCWE-362

CVE-2026-34363: Parse Server: LiveQuery protected field leak via shared mutable state across concurrent subscribers

parse-community · parse-server

Affected: parse-community parse-server · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
31st percentile
050100

Higher than 31% of scored CVEs

8.2HighCVSS 4.0
LowHigh

DescriptionCVE.org

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.65 and 9.7.0-alpha.9, when multiple clients subscribe to the same class via LiveQuery, the event handlers process each subscriber concurrently using shared mutable objects. The sensitive data filter modifies these shared objects in-place, so when one subscriber's filter removes a protected field, subsequent subscribers may receive the already-filtered object. This can cause protected fields and authentication data to leak to clients that should not see them, or cause clients that should see the data to receive an incomplete object. Additionally, when an afterEvent Cloud Code trigger is registered, one subscriber's trigger modifications can leak to other subscribers through the same shared mutable state. Any Parse Server deployment using LiveQuery with protected fields or afterEvent triggers is affected when multiple clients subscribe to the same class. This issue has been patched in versions 8.6.65 and 9.7.0-alpha.9.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • parse-community · parse-server< 8.6.65; >= 9.0.0, < 9.7.0-alpha.9

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
March 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-34363 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References