Read the docs
TI-2026-26649 Aliases CVE-2026-34363GHSA-m983-v2ff-wq65

Parse Server: LiveQuery protected field leak via shared mutable state across concurrent subscribers

Priority LOW 36CWE-362Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00373 31st percentileScored 2026-11-07
Fix Fixed parse-server (parse-community): 8.6.65, 9.7.0-alpha.9parse-server (npm): 9.7.0-alpha.9, 8.6.65

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
parse-communityparse-serverbefore 8.6.65; 9.0.0 to before 9.7.0-alpha.98.6.65, 9.7.0-alpha.9Patch availableCNA
—parse-server (npm)9.0.0 to before 9.7.0-alpha.99.7.0-alpha.9Patch availableGHSA-m983-v2ff-wq65
—parse-server (npm)before 8.6.658.6.65Patch availableGHSA-m983-v2ff-wq65
  • parse-server Vendorparse-community Affected before 8.6.65; 9.0.0 to before 9.7.0-alpha.9 Fixed in 8.6.65, 9.7.0-alpha.9 Patch available CNA
  • parse-server (npm) Vendor— Affected 9.0.0 to before 9.7.0-alpha.9 Fixed in 9.7.0-alpha.9 Patch available GHSA-m983-v2ff-wq65
  • parse-server (npm) Vendor— Affected before 8.6.65 Fixed in 8.6.65 Patch available GHSA-m983-v2ff-wq65

CPE configurations NVD · 9

CPEVersionsRoleVendor
cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*before 8.6.65; 9.0.0 to before 9.7.0Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha1:*:*:*:node.js:*:*9.7.0 alpha1Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha2:*:*:*:node.js:*:*9.7.0 alpha2Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha3:*:*:*:node.js:*:*9.7.0 alpha3Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha4:*:*:*:node.js:*:*9.7.0 alpha4Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha5:*:*:*:node.js:*:*9.7.0 alpha5Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha6:*:*:*:node.js:*:*9.7.0 alpha6Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha7:*:*:*:node.js:*:*9.7.0 alpha7Vulnerableparse-community
cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha8:*:*:*:node.js:*:*9.7.0 alpha8Vulnerableparse-community
  • cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:* Versions before 8.6.65; 9.0.0 to before 9.7.0 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha1:*:*:*:node.js:*:* Versions 9.7.0 alpha1 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha2:*:*:*:node.js:*:* Versions 9.7.0 alpha2 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha3:*:*:*:node.js:*:* Versions 9.7.0 alpha3 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha4:*:*:*:node.js:*:* Versions 9.7.0 alpha4 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha5:*:*:*:node.js:*:* Versions 9.7.0 alpha5 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha6:*:*:*:node.js:*:* Versions 9.7.0 alpha6 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha7:*:*:*:node.js:*:* Versions 9.7.0 alpha7 Vulnerable ·parse-community
  • cpe:2.3:a:parseplatform:parse-server:9.7.0:alpha8:*:*:*:node.js:*:* Versions 9.7.0 alpha8 Vulnerable ·parse-community

Remediation

  • Fix · CNA parse-server (parse-community) Fixed in 8.6.65, 9.7.0-alpha.9
  • Fix · GHSA-m983-v2ff-wq65 parse-server (npm) Fixed in 9.7.0-alpha.9 Advisory →
  • Fix · GHSA-m983-v2ff-wq65 parse-server (npm) Fixed in 8.6.65 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-34363
  2. 2026-10-03 Alias added: GHSA-m983-v2ff-wq65

References

  • TI-2022-08574 Command Injection in Parse server CVSS 3.1CRITICAL 10.0
  • TI-2024-18136 Parse Server literalizeRegexPart SQL Injection CVSS 3.1CRITICAL 10.0
  • TI-2022-18768 Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser CVSS 3.1CRITICAL 9.8
  • TI-2024-31550 Parse Server's custom object ID allows to acquire role privileges CVSS 3.1HIGH 8.1
  • TI-2023-18316 Parse Server vulnerable to remote code execution via MongoDB BSON parser through prototype pollution CVSS 3.1CRITICAL 9.8
  • TI-2026-23790 Parse Server session token exfiltration via `redirectClassNameForKey` query parameter CVSS 4.0CRITICAL 9.9
See all 101 →

Sources