How severe is GHSA-j7mm-f4rv-6q6q?

No CVSS score has been assigned to GHSA-j7mm-f4rv-6q6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j7mm-f4rv-6q6q?

GHSA-j7mm-f4rv-6q6q affects the following packages: parse-server (npm), parse-server (npm). Ecosystems affected: npm.

How do I fix GHSA-j7mm-f4rv-6q6q?

Update parse-server to 9.6.0-alpha.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7mm-f4rv-6q6q is resolved across your whole dependency graph.

How do I detect GHSA-j7mm-f4rv-6q6q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j7mm-f4rv-6q6q if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-j7mm-f4rv-6q6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-j7mm-f4rv-6q6q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j7mm-f4rv-6q6q?

GHSA-j7mm-f4rv-6q6q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j7mm-f4rv-6q6q?

GHSA-j7mm-f4rv-6q6q is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j7mm-f4rv-6q6q published, and has it been updated?

GHSA-j7mm-f4rv-6q6q was published on March 12, 2026 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Parse Server has a protected fields bypass via LiveQuery subscription WHERE clauseGHSA-j7mm-f4rv-6q6q

GHSA-j7mm-f4rv-6q6q is a Information Exposure vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below.

Also known asBIT-parse-2026-32098CVE-2026-32098

Published

Mar 12, 2026

Updated

Mar 14, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j7mm-f4rv-6q6q.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

62other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

parse-servernpm

50Kdownloads / week

Description

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`parse-server`	≥ 9.0.0&&< 9.6.0-alpha.9	9.6.0-alpha.9`npm install parse-server@9.6.0-alpha.9`
📦npm	`parse-server`	all versions	8.6.35`npm install parse-server@8.6.35`

Affected Products

1 product · 10 configurations

Application

parse-serverparseplatform

≥ 9.0.0 && < 9.6.0

1 version

9.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-server to 9.6.0-alpha.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7mm-f4rv-6q6q is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### 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 ag