Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.9.1-alpha.13 and 8.6.83, a LiveQuery subscriber could receive object field values they were not authorized to read when a single save changed both an object field and the subscriber's ACL read access, because leave and enter events included the wrong object state. This issue is fixed in versions 9.9.1-alpha.13 and 8.6.83.
CVE-2026-57481
This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.3
- EG Score
- 2.3(medium)
- EPSS
- 30.7%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
References (7)
- security-advisories@githubhttps://github.com/parse-community/parse-server/commit/c9b24cecfee76d8563019adaacbcbd78471dc41e
- security-advisories@githubhttps://github.com/parse-community/parse-server/commit/e9c85dfe40a866a55ebae3b6ae56285ac0a22e64
- security-advisories@githubhttps://github.com/parse-community/parse-server/pull/10515
- security-advisories@githubhttps://github.com/parse-community/parse-server/pull/10516
- security-advisories@githubhttps://github.com/parse-community/parse-server/releases/tag/8.6.83
- security-advisories@githubhttps://github.com/parse-community/parse-server/releases/tag/9.9.1-alpha.13
- security-advisories@githubhttps://github.com/parse-community/parse-server/security/advisories/GHSA-97pr-9hgg-3p8r
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| parse-server | — | 9.9.1-alpha.13 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-07-11 16:35 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 21:11 UTCEG score recompute
- 2026-07-08 21:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-200
Frequently asked(5)
What is CVE-2026-57481?
When was CVE-2026-57481 disclosed?
Is CVE-2026-57481 actively exploited?
What is the CVSS score of CVE-2026-57481?
How do I remediate CVE-2026-57481?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57481
Is Your Infrastructure Affected by CVE-2026-57481?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.