Live › vulnerability › CVE-2026-120310
Parse Server returns stored field values in object update responses without checking read permission. A client allowed to update an object but not read it can see its data, including results of atomic operations and values set by Cloud Code triggers.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 03:31 UTC. All times on this page are UTC.
Applications that run Parse Server and use class-level permissions or object ACLs that let clients update objects without letting them read them. Deployments where every writable object is also readable by the same client are not exposed in the same way. The sources do not say whether managed Parse hosting is patched.
No product ranges from the sources yet.
npm ls parse-server or the version field in node_modules/parse-server/package.json.8.6.109 and later in the 8.x line.9.10.6-alpha.1 and later in the 9.x line; through are affected.9.0.09.10.6-alpha.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Parse Server before 8.6.109 and 9.0.0 before 9.10.6-alpha.1 returns stored field values in object update responses without checking read access, so clients whose class-level permissions or object ACLs allow update but not read can see object data. Attackers can update such objects to read atomic operation results (Increment, Add, AddUnique, Remove), Cloud Code trigger-set values, and, for dot notation keys under certain conditions, the whole stored parent field.
This page as .md · .json · in your agent: get_signal("CVE-2026-120310")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.