CVE-2026-57481: parse-server · Information Exposure
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 9.9.1-alpha.13 or 8.6.83 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.9.1-alpha.13, 8.6.83
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade parse-server to 9.9.1-alpha.13 or 8.6.83; parse-server to 8.6.83.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-server | Affected
| Fixed in
|
| parse-communityparse-server | Affected
| Fixed in
|
npmparse-serverpkg:npm/parse-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade parse-server to version 8.6.83 or later, or 9.9.1-alpha.13 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory stating the issue is resolved in these versions. No additional mitigation is indicated.
Description
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.
References
- github.com/parse-community/parse-server/security/advisories/GHSA-97pr-9hgg-3p8r (opens in a new tab)
- github.com/parse-community/parse-server/pull/10515 (opens in a new tab)
- github.com/parse-community/parse-server/pull/10516 (opens in a new tab)
- github.com/parse-community/parse-server/commit/c9b24cecfee76d8563019adaacbcbd78471dc41e (opens in a new tab)
- github.com/parse-community/parse-server/commit/e9c85dfe40a866a55ebae3b6ae56285ac0a22e64 (opens in a new tab)
- github.com/parse-community/parse-server/releases/tag/8.6.83 (opens in a new tab)
- github.com/parse-community/parse-server/releases/tag/9.9.1-alpha.13 (opens in a new tab)