CVE-2026-32248

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.12 and 8.6.38, an unauthenticated attacker can take over any user account that was created with an authentication provider that does not validate the format of the user identifier (e.g. anonymous authentication). By sending a crafted login request, the attacker can cause the server to perform a pattern-matching query instead of an exact-match lookup, allowing the attacker to match an existing user and obtain a valid session token for that user's account. Both MongoDB and PostgreSQL database backends are affected. Any Parse Server deployment that allows anonymous authentication (enabled by default) is vulnerable. This vulnerability is fixed in 9.6.0-alpha.12 and 8.6.38.

CVSS v3
9.8
EG Score
9.8(low)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

March 12, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available. Sources: github_release, github.
github Patch Available

Account takeover via operator injection in authentication data identifier · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-5fw2-8jcv-xh87
github_release Patch Available

9.6.0-alpha.12

Patch available: parse-community/parse-server 9.6.0-alpha.12 (pre-release)

https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.12
github_release Patch Available

8.6.38

Patch available: parse-community/parse-server 8.6.38

https://github.com/parse-community/parse-server/releases/tag/8.6.38

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× 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-08-01 04:16 UTCEPSS rescore
  2. 2026-07-30 16:28 UTCEPSS rescore
  3. 2026-07-30 01:30 UTCEPSS rescore
  4. 2026-07-27 13:39 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32248?
CVE-2026-32248 is a critical vulnerability published on March 12, 2026. 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.12 and 8.6.38, an unauthenticated attacker can take over any user account that was created with an authentication provider that does not validate the format of the user…
When was CVE-2026-32248 disclosed?
CVE-2026-32248 was first published in the National Vulnerability Database on March 12, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32248 actively exploited?
CVE-2026-32248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.4% of all scored CVEs.
What is the CVSS score of CVE-2026-32248?
CVE-2026-32248 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-32248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32248, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-32248?

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

Start Free Scan →Browse All CVEs