Skip to main content
VulnerabilityPublished

CVE-2026-134243: parse-server · Incorrect Authorization

Affects parse-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 9.11.1-alpha.2 when convenient.

Data as of 21 Nov 2026, 16:44 UTC

CVSS 4.0 base score
2.3Low
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.02.3
CNA (VulnCheck)CVSS 3.13.1
Patch
Available – fixed in 9.11.1-alpha.2, 8.6.122
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/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 20 Nov 2026.

What to do

Upgrade parse-server to 9.11.1-alpha.2; parse-server to 8.6.122; parse-server to 9.11.1-alpha.2 or 8.6.122.

Affected software

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

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.122 and 9.0.0 before 9.11.1-alpha.2 does not prevent dot notation keys from changing a field that a beforeSave trigger keeps constant or reverts, affecting Object, Array, GeoPoint, Polygon, Bytes (on MongoDB), and ACL fields on create and update. A client allowed to write the object can modify such a field, such as a constant role list, to bypass Cloud Code authorization checks.

References

Community reviews

Loading reviews…