Parse Server before 8.6.99 and 9.x before 9.10.3 Information Disclosure via User Update

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source

EPSS

• CVE-2026-112768: 0.40% estimated exploitation activity in the next 30 days; percentile 34.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Parse Server before 8.6.99 and 9.0.0 before 9.10.3 evaluates checks against the target account during a user update before authorizing the caller, and reflects their outcome in the response. An unauthorized caller, with or without a session, can confirm guessed usernames or emails and, when passwordPolicy.maxPasswordHistory or doNotAllowUsername is set, guessed current or previous passwords, bypassing account lockout.

Published by the source

26 Oct 2026, 11:15 UTC

Last modified by the source

26 Oct 2026, 11:55 UTC

Source last checked

26 Oct 2026, 12:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from osv record BIT-parse-2026-112768

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-112768

Advisory: Parse Server before 8.6.99 and 9.x before 9.10.3 Information Disclosure via User Update
IDs: CVE-2026-112768, GHSA-p49q-9w65-f9p7
Record: https://patchnext.com/advisories/cve-2026-112768 (revision 1, source checked 26 Oct 2026, 12:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: parse 9.10.3, 8.6.99. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami parse: affected < 8.6.99; >= 9.0.0, < 9.10.3; fixed in 8.6.99, 9.10.3

## Suggested inspection (read-only)
- Bitnami parse: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on parse.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/BIT-parse-2026-112768 (OSV record BIT-parse-2026-112768 lists affected ranges: Bitnami parse >=0 =9.0.0 <9.10.3 (fixed))

Commands are suggestions: review each one before running it.