🛡️ CVE-2026-33539 — parse

🟠 CVSS 8.0 — High ✅ No Known Exploit OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Parse Server has SQL Injection through aggregate and distinct field names in PostgreSQL adapter

Impact

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.

Patches

Field names in the aggregate $group._id object values and distinct dot-notation parameters are now validated to only contain alphanumeric characters and underscores, preventing SQL injection via the :raw interpolation used in the PostgreSQL storage adapter.

Workarounds

No workaround. Upgrade to a patched version.

Affected software

CVE-2026-33539 is recorded against 2 packages.

  • parse
  • parse-server

Timeline and source

Published on 27 March 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
nvd.nist.gov (Web)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-03-27
Updated 2026-08-12
Modified 2026-03-27
Fix URL N/A

Affected Packages

Software From version Fixed in
parse
parse-server

Similar Threats

Site Security Check

Is parse part of your stack?

CVE-2026-33539 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.