Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.59 and 9.6.0-alpha.53, an attacker with master key access can execute arbitrary SQL statements on the PostgreSQL database by injecting SQL metacharacters into field name parameters of the aggregate $group pipeline stage or the distinct operation. This allows privilege escalation from Parse Server application-level administrator to PostgreSQL database-level access. Only Parse Server deployments using PostgreSQL are affected. MongoDB deployments are not affected. This issue has been patched in versions 8.6.59 and 9.6.0-alpha.53.
CVE-2026-33539
This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 63% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(medium)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity72% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
March 24, 2026
Last Modified
June 17, 2026
Advisory Details (5)
Auto-updated Aug 4, 2026SQL injection via aggregate and distinct field names in PostgreSQL adapter · Advisory · parse-community/parse-server · GitHub
https://github.com/parse-community/parse-server/security/advisories/GHSA-p2w6-rmh7-w8q3fix: SQL injection via aggregate and distinct field names in PostgreSQL adapter (GHSA-p2w6-rmh7-w8q3)
Patch available: parse-community/parse-server 8.6.81 (PR #10273 merged 2026-03-21)
https://github.com/parse-community/parse-server/pull/10273fix: SQL injection via aggregate and distinct field names in PostgreSQL adapter (GHSA-p2w6-rmh7-w8q3)
Patch available: parse-community/parse-server 9.9.1-alpha.6 (PR #10272 merged 2026-03-21)
https://github.com/parse-community/parse-server/pull/10272commit bdddab5f8b61 (parse-community/parse-server)
Patch available: parse-community/parse-server 9.9.1-alpha.6 (contains commit bdddab5f8b61)
https://github.com/parse-community/parse-server/commit/bdddab5f8b61a40cb8fc62dd895887bdd2f3838ecommit 03249f9bf5b8 (parse-community/parse-server)
Patch available: parse-community/parse-server 8.6.81 (contains commit 03249f9bf5b8)
https://github.com/parse-community/parse-server/commit/03249f9bf5b8783c8b848f84dab791ff0b761b8cAffected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| parse-server | — | 8.6.59 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 32× 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.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 15:08 UTCOSV refresh
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
Show 41 moreShow fewer
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:31 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:49 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:29 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 21:07 UTCEG score recompute
- 2026-08-11 04:08 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 17:19 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:25 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 16:44 UTCEG score recompute
- 2026-08-06 19:04 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 01:10 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 23:55 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 15:44 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:29 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-33539?
When was CVE-2026-33539 disclosed?
Is CVE-2026-33539 actively exploited?
What is the CVSS score of CVE-2026-33539?
How do I remediate CVE-2026-33539?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33539
Is Your Infrastructure Affected by CVE-2026-33539?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.