Information Exposure Affecting parse-server package, versions >=9.0.0 <9.10.6-alpha.1<8.6.109
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Information Exposure vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-PARSESERVER-22132602
- published2 Nov 2026
- disclosed2 Nov 2026
- creditUnknown
Introduced: 2 Nov 2026
NewCVE-2026-120310 (opens in a new tab)How to fix?
Upgrade parse-server to version 9.10.6-alpha.1, 8.6.109 or higher.
Overview
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js.
Affected versions of this package are vulnerable to Information Exposure in the object update response handler in RestWrite.js when a client updates an object it lacks read access to. The server returns stored field values in update responses without checking read permissions, so a caller whose class-level permissions or object ACL grant update but not read access can observe object data. This includes results of atomic operations (Increment, Add, AddUnique, Remove), values set by Cloud Code triggers, and, for dot-notation key updates under certain conditions (a beforeSave or afterSave trigger is present, or on MongoDB for array-index operations), the entire stored parent field.
Note: This is only exploitable when a client has been granted update permission via class-level permissions or write access via an object ACL, but has not been granted read/get access to the same object.
Workaround
Do not grant update permission through class-level permissions, or write access through object ACLs, to clients that must not read the stored values of the object.