Skip to main content
VulnerabilityPublished

CVE-2026-119570: Parse Server 9.7.0 before 9.10.5 Protected Field Exposure in Save Responses

Affects parseSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119570· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 9.10.5 when convenient.

Data as of 17 Nov 2026, 16:21 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.10.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 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 16 Nov 2026.

What to do

Upgrade parse to 9.10.5.

Affected software

ProductAffectedFixed in
Bitnamiparsepkg:bitnami/parseOther threatsAffected
  • >=9.7.0 <9.10.5
Fixed in
  • 9.10.5

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

AI-suggested

Upgrade Parse Server to version 9.10.5 or later, where this vulnerability is fixed. Since a patch is available, applying this official fix is the recommended mitigation.

Description

Parse Server versions from 9.7.0 up to but not including 9.10.5 have an information disclosure vulnerability. This flaw allows clients with create or update permissions to read protected field values written by beforeSave triggers when the protectedFieldsSaveResponseExempt setting is false. The issue arises because clients can access these protected fields using dot notation keys in the same request. The vulnerability is fixed in version 9.10.5.

References

Community reviews

Loading reviews…