What is the CVSS score of CVE-2026-32098?

CVE-2026-32098 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-32098?

Within 24 hours: Inventory all Parse Server deployments and identify instances with LiveQuery enabled and class-level protected fields configured. Within 7 days: Implement the primary workaround (disable LiveQuery) or apply network-based restrictions limiting LiveQuery access; conduct data exposure assessment for affected systems. Within 30 days: Monitor vendor announcements for patch availability and establish a patching timeline; implement comprehensive access control audits across all protected data classes.

Parse Server CVE-2026-32098

HIGH

Information Exposure (CWE-200)

2026-03-11 security-advisories@github.com

GHSA-j7mm-f4rv-6q6q

Information Disclosure Node.js AI / ML Parse Server Parseplatform

7.5

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Subscribe to LiveQuery with WHERE clause
Exploit

Reference protected field via dot-notation or $regex
Execution

Observe event delivery pattern
Impact

Infer protected field values through boolean oracle

Vulnerability Assessment

Weakness	CWE CWE-200 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V14 - Data Protection Data exposure prevention MITRE ATT&CK 2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Parse Server instances with protectedFields configured on classes and LiveQuery subscriptions enabled. No authentication required against default deployments exposing LiveQuery endpoints.
Impact	Exposed information (credentials, internal paths, user data, configuration) can be leveraged for further attacks or regulatory violations.
Exploit ScenarioDerived	An attacker triggers error conditions or accesses improperly protected endpoints to extract sensitive internal information from the application.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Impact

An attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them. 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.

Patches

The fix adds validation of the LiveQuery subscription WHERE clause against the class's protected fields, mirroring the existing REST API validation. If a subscription's WHERE clause references a protected field directly, via dot-notation, or inside $or / $and / $nor operators, the subscription is rejected with a permission error. This is applied during subscription creation, so existing event delivery paths are not affected.

Workarounds

Disable LiveQuery for classes that use protectedFields in their Class-Level Permissions, or remove protectedFields from classes that require LiveQuery.

References

GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-j7mm-f4rv-6q6q
Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.9
Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.35

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:07 CVSS 7.5

RemediationAI

Implement proper access controls. Sanitize error messages in production. Review logging practices to avoid capturing sensitive data.

Affected Packages

npm parse-server fix: 8.6.35, 9.6.0-alpha.9

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Information disclosure occurs when an application inadvertently reveals sensitive data to unauthorized actors through error messages, logs, or improper access controls. This vulnerability is classified as Information Exposure (CWE-200).

Know when Parse Server gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

CVE Published

Mar 11, 2026 - 20:16 nvd

HIGH 7.5

DescriptionGitHub Advisory

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. 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.

Executive ViewAI

Why It Matters

A vulnerability in Parse Server's LiveQuery feature allows attackers to bypass access controls and discover sensitive protected field values through subscription manipulation. Organizations using Parse Server with both protected fields and LiveQuery enabled risk unauthorized data exposure and potential compliance violations.

Business Impact: High

Compensating Controls

Disable LiveQuery feature entirely if not critical to operations; restrict LiveQuery endpoint access via network firewall/WAF to trusted applications only; implement API rate limiting and anomaly detection on subscription requests; conduct audit logs review for suspicious LiveQuery subscription patterns; apply principle of least privilege to service accounts accessing LiveQuery; consider temporary application of query filtering at the API gateway layer to block WHERE clauses targeting protected fields.

Threat Intelligence Overview

EPSS Score

0.0%

Top 88% exploitable

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.