Skip to main content
CVE-2026-134242VulnerabilityPublished

Parse Server 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1 does not handle a failure to serialize an object after a beforeSave trigger, leaving the request unsettled and terminating the server process

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134242· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 9.11.1-alpha.1 soon.

Data as of 21 Nov 2026, 19:14 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.15.9
Patch
Available – fixed in 9.11.1-alpha.1, 8.6.121
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 21 Nov 2026.

What to do

Upgrade parse-server to 9.11.1-alpha.1; parse-server to 8.6.121; parse-server to 9.11.1-alpha.1 or 8.6.121.

Affected software

ProductAffectedFixed in
parse-communityparse-serverAffected
  • >=9.0.0 <9.11.1-alpha.1
Fixed in
  • 9.11.1-alpha.1
parse-communityparse-serverAffected
  • >=2.5.0 <8.6.121
Fixed in
  • 8.6.121
npmparse-serverpkg:npm/parse-serverOther threatsAffected
  • >=9.0.0 <9.11.1-alpha.1
  • >=2.5.0 <8.6.121
Fixed in
  • 9.11.1-alpha.1
  • 8.6.121

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

Description

Parse Server 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1 does not handle a failure to serialize an object after a beforeSave trigger, leaving the request unsettled and terminating the server process. A remote attacker able to update an object in a class with a beforeSave trigger can send a dot notation key below a non-object field, such as a timestamp, to crash the server for all clients.

References

Community reviews

Loading reviews…