CVE-2026-33539 is a SQL injection vulnerability in Parse Server affecting PostgreSQL-backed deployments prior to versions 8.6.59 and 9.6.0-alpha.53. The flaw is reachable when field name parameters supplied to the aggregate $group pipeline stage or the distinct operation are not safely handled, allowing SQL metacharacters to be injected into backend PostgreSQL queries. An attacker who already possesses Parse Server master key access can exploit this condition to execute arbitrary SQL statements directly against the PostgreSQL database. The issue results in a privilege boundary break between Parse Server application-level administrative access and the underlying database layer. MongoDB deployments are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.