Skip to main content
VulnerabilityPublished

CVE-2026-121414: parse-server · Uncaught Exception

Affects parse-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 9.10.6-alpha.2 soon.

Data as of 3 Nov 2026, 14:43 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.10.6-alpha.2, 8.6.110
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 3 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 3 Nov 2026.

What to do

Upgrade parse-server to 9.10.6-alpha.2; parse-server to 8.6.110; parse-server to 9.10.6-alpha.2 or 8.6.110.

Affected software

ProductAffectedFixed in
parse-communityparse-serverAffected
  • >=9.0.0 <9.10.6-alpha.2
Fixed in
  • 9.10.6-alpha.2
parse-communityparse-serverAffected
  • <8.6.110
Fixed in
  • 8.6.110
npmparse-serverpkg:npm/parse-serverOther threatsAffected
  • >=9.0.0 <9.10.6-alpha.2
  • <8.6.110
Fixed in
  • 9.10.6-alpha.2
  • 8.6.110

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

Description

Parse Server before 8.6.110 and 9.0.0 before 9.10.6-alpha.2 fails to contain a serialization error when an object update uses a dot notation key targeting a pointer field's object identifier on a class with an afterSave trigger. Attackers, including unauthenticated clients when objects are writable without a session, can send such an update to crash the Node process.

References

Community reviews

Loading reviews…