# CVE-2026-57481: Parse Server: LiveQuery discloses object data to a subscriber across an ACL read-access change

> Parse Server LiveQuery subscribers can view unauthorized object data when ACLs and fields change simultaneously, exposing sensitive information to unauthorized users.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** BIT-parse-2026-57481, GHSA-97pr-9hgg-3p8r

## What is CVE-2026-57481?

CVE-2026-57481 is a low-severity vulnerability in parse-community parse-server, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-57481?

5 open source packages ship an affected version, including parse-server and parse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse-server` | npm | All versions | 8.6.83 |
| `parse-server` | npm | All versions | 8.6.83 |
| `parse-server` | npm | From 9.0.0 | 9.9.1-alpha.13 |
| `parse-server` | npm | From 9.0.0 | 9.9.1-alpha.13 |
| `parse` | Bitnami | All versions | 8.6.83, 9.9.1 |

## How do I fix CVE-2026-57481?

Upgrade parse-server to a fixed version for your release line: 8.6.83 or 9.9.1-alpha.13.

## Is CVE-2026-57481 being exploited?

There is no known exploitation of CVE-2026-57481 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57481 and fix it if it is affected.

What it is: CVE-2026-57481 is a low-severity vulnerability in parse-community parse-server, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57481 in the wild and no public exploit code.

Affected packages and fixed versions:
- parse-server (npm): affected all versions; fixed in 8.6.83
- parse-server (npm): affected all versions; fixed in 8.6.83
- parse-server (npm): affected from 9.0.0; fixed in 9.9.1-alpha.13
- parse-server (npm): affected from 9.0.0; fixed in 9.9.1-alpha.13
- parse (Bitnami): affected all versions; fixed in 8.6.83, 9.9.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57481/ (Markdown: https://insights.sbomify.com/CVE-2026-57481/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57481
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57481
- OSV: https://osv.dev/vulnerability/CVE-2026-57481

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57481/
Summaries are generated and may contain mistakes; the official description above is the record.