CVE-2026-32234

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.7 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. 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: epss, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: 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.10 and 8.6.36, an attacker with access to the master key can inject malicious SQL via crafted field names used in query constraints when Parse Server is configured with PostgreSQL as the database. The field name in a $regex query operator is passed to PostgreSQL using unparameterized string interpolation, allowing the attacker to manipulate the SQL query. While the master key controls what can be done through the Parse Server abstraction layer, this SQL injection bypasses Parse Server entirely and operates at the database level. This vulnerability only affects Parse Server deployments using PostgreSQL. This vulnerability is fixed in 9.6.0-alpha.10 and 8.6.36.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

March 11, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_release, github.
github Patch Available

SQL injection via query field name when using PostgreSQL · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-c442-97qw-j6c6
github_release Patch Available

9.6.0-alpha.10

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

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

8.6.36

Patch available: parse-community/parse-server 8.6.36

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
parse-server—8.6.36—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 20:10 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 35 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 11:50 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 07:48 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 22:58 UTCEG score recompute
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 05:42 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 06:40 UTCEG score recompute
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-07 18:15 UTCEG score recompute
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 02:01 UTCEG score recompute
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-04 15:10 UTCEPSS rescore
  26. 2026-08-04 10:38 UTCEPSS rescore
  27. 2026-08-04 01:19 UTCEG score recompute
  28. 2026-08-03 10:36 UTCEPSS rescore
  29. 2026-08-02 17:29 UTCEG score recompute
  30. 2026-08-02 02:27 UTCEPSS rescore
  31. 2026-08-01 04:16 UTCEPSS rescore
  32. 2026-07-30 16:28 UTCEPSS rescore
  33. 2026-07-30 01:30 UTCEPSS rescore
  34. 2026-07-28 15:36 UTCEPSS rescore
  35. 2026-07-27 13:41 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32234?
CVE-2026-32234 is a medium vulnerability published on March 11, 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.10 and 8.6.36, an attacker with access to the master key can inject malicious SQL via crafted field names used in query constraints when Parse Server is configured with…
When was CVE-2026-32234 disclosed?
CVE-2026-32234 was first published in the National Vulnerability Database on March 11, 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-32234 actively exploited?
CVE-2026-32234 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.6% of all scored CVEs.
What is the CVSS score of CVE-2026-32234?
CVE-2026-32234 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-32234?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32234, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32234

Explore →

Is Your Infrastructure Affected by CVE-2026-32234?

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

Start Free Scan →Browse All CVEs