CVE-2026-100632

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Parse Server is an open-source backend server. In versions >= 9.0.0 and < 9.10.1-alpha.8, and in versions < 8.6.89, LiveQuery evaluates the protectedFields class-level permission against an incompletely resolved caller identity: the subscriber's roles are not resolved, and when a subscription does not supply its own session token the event payload is redacted against an anonymous identity even though the read was authorized against the connected user. As a result, field masks defined for a role, for authenticated users, or for a specific user are not applied, so an authenticated subscriber can receive field values that the REST API correctly withholds and can use a masked field to filter or watch a subscription. Only classes with LiveQuery enabled that define protectedFields under a role:, authenticated, or per-user group are affected; masks under the public (*) group are applied correctly. The issue is fixed in 9.10.1-alpha.8 and 8.6.89. As a workaround, additionally define the affected field masks under the public (*) group, or disable LiveQuery for classes whose class-level permissions rely on role-scoped, authenticated, or per-user protectedFields groups.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
Patch available. Sources: github.
generic

Parse Server 9.0.0 before 9.10.1 Protected Fields Disclosure via LiveQuery | Advisories | VulnCheck

https://www.vulncheck.com/advisories/parse-server-9.0.0-before-9.10.1-protected-fields-disclosure-via-livequery
github Patch Available

LiveQuery discloses protected fields by resolving an incomplete subscriber identity · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-9jpp-xhh6-75mf

Vendor Advisories for CVE-2026-100632(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 08:08 UTCEG score recompute
  2. 2026-10-04 08:08 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 10:28 UTCEG score recompute
  5. 2026-10-03 10:28 UTCGHSA enrichment
  6. 2026-10-02 12:47 UTCEG score recompute
  7. 2026-10-02 12:47 UTCGHSA enrichment
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-10-01 15:07 UTCGHSA enrichment
  10. 2026-09-30 17:27 UTCEG score recompute
  11. 2026-09-30 17:27 UTCGHSA enrichment
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-30 13:07 UTCGHSA enrichment
  14. 2026-09-29 15:26 UTCEG score recompute
  15. 2026-09-29 15:26 UTCGHSA enrichment
  16. 2026-09-29 15:20 UTCEPSS rescore
  17. 2026-09-28 17:43 UTCEG score recompute
  18. 2026-09-28 17:42 UTCGHSA enrichment
  19. 2026-09-28 17:00 UTCEG score recompute
  20. 2026-09-28 17:00 UTCGHSA enrichment
  21. 2026-09-28 13:50 UTCEPSS rescore
  22. 2026-09-28 09:55 UTCEG score recompute
  23. 2026-09-28 09:55 UTCGHSA enrichment
  24. 2026-09-27 12:15 UTCEG score recompute
  25. 2026-09-27 12:15 UTCGHSA enrichment
Show 3 more
  1. 2026-09-26 14:34 UTCEG score recompute
  2. 2026-09-26 13:40 UTCEG score recompute
  3. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100632?
CVE-2026-100632 is a medium vulnerability published on September 26, 2026. Parse Server is an open-source backend server. In versions >= 9.0.0 and < 9.10.1-alpha.8, and in versions < 8.6.89, LiveQuery evaluates the protectedFields class-level permission against an incompletely resolved caller identity: the subscriber's roles are not resolved, and when a subscription does…
When was CVE-2026-100632 disclosed?
CVE-2026-100632 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100632 actively exploited?
CVE-2026-100632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100632?
CVE-2026-100632 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100632?
A fix for CVE-2026-100632 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100632 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100632

Explore →

Is Your Infrastructure Affected by CVE-2026-100632?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs