CVE-2026-32098
Published: 11 March 2026
Summary
CVE-2026-32098 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Parseplatform Parse-Server. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 15.3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Automated marking applies security attributes to system outputs, making it harder for attackers to exploit unmarked sensitive information leading to unauthorized exposure.
Proper attribute retention and permitted-value enforcement limits unauthorized actors from accessing sensitive information lacking correct labels.
Prevents unauthorized exposure of sensitive information by prohibiting untrusted external systems from processing or storing it.
By enforcing authorization matching prior to sharing, the control reduces the risk of exposing sensitive information to unauthorized actors.
Review and removal of nonpublic information from publicly accessible systems directly prevents exposure of sensitive data to unauthorized actors.
Data mining protection mechanisms detect and block unauthorized bulk extraction of sensitive data, directly mitigating exposure to unauthorized actors.
Literacy training teaches users to recognize and avoid actions that result in unauthorized exposure of sensitive information.
Retaining and monitoring training records confirms personnel have completed privacy and security awareness training on handling sensitive data, reducing the chance of unauthorized exposure due to lack of knowledge.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Remote unauthenticated exploitation of public-facing Parse Server (AV:N/PR:N) to leak protected data via LiveQuery oracle queries directly matches T1190; no other techniques are directly enabled by the described information disclosure mechanism.
NVD Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.9 and 8.6.35, an attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them.…
more
By subscribing with a WHERE clause that references a protected field (including via dot-notation or $regex), the attacker can observe whether LiveQuery events are delivered for matching objects. This creates a boolean oracle that leaks protected field values. The attack affects any class that has both protectedFields configured in Class-Level Permissions and LiveQuery enabled. This vulnerability is fixed in 9.6.0-alpha.9 and 8.6.35.
Deeper analysisAI
CVE-2026-32098 is an information disclosure vulnerability (CWE-200) in Parse Server, an open source backend deployable on any Node.js-compatible infrastructure. In versions prior to 9.6.0-alpha.9 and 8.6.35, attackers can exploit LiveQuery subscriptions to infer values of protected fields without direct access. This occurs by crafting WHERE clauses in subscriptions that reference protected fields—via direct access, dot-notation, or $regex operators—and observing whether LiveQuery events are delivered for matching objects, effectively creating a boolean oracle that leaks sensitive data. The issue impacts any class configured with protectedFields in Class-Level Permissions (CLP) where LiveQuery is enabled.
The vulnerability carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high confidentiality impact with no privileges, user interaction, or scope change required. Unauthenticated remote attackers can exploit it over the network with low complexity by establishing LiveQuery subscriptions and iteratively querying protected fields to deduce their values through event delivery patterns.
Parse Server addresses this in releases 9.6.0-alpha.9 and 8.6.35, as detailed in the project's GitHub security advisory (GHSA-j7mm-f4rv-6q6q) and corresponding release notes. Security practitioners should upgrade affected deployments to these versions to mitigate the oracle-based leakage.
Details
- CWE(s)