# CVE-2026-119125: Parse Server before 8.6.107 and 9.0.0 before 9.10.5-alpha.8 Information Disclosure via beforeSave Reverted Fields


- **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
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-9rvr-f5hc-9f2f, GHSA-w9vv-f4q5-5fgr

## What is CVE-2026-119125?

CVE-2026-119125 is a low-severity vulnerability in parse-community parse-server, published on 29 Oct 2026. 

### Official description

Parse Server before 8.6.107 and 9.0.0 before 9.10.5-alpha.8 returns the stored value of a field reverted by a beforeSave trigger in object update responses, even to clients without read access to that object or field. An authenticated client able to update an object whose beforeSave trigger reverts a field, via revert() or a constant: true validator, can read protected values, including its own account's raw MFA authData when protectedFieldsTriggerExempt is enabled.

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

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


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

No fix has been published for CVE-2026-119125 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119125 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119125 is a low-severity vulnerability in parse-community parse-server, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119125 in the wild and no public exploit code.

Affected product: parse-community parse-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-119125/ (Markdown: https://insights.sbomify.com/CVE-2026-119125/index.md)
```

## Sources

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

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