CVE-2026-112768: Parse Server user update information disclosure

CVE-2026-112768 · Severity: info · Published 2026-10-19

Parse Server is a backend framework that manages user accounts and authentication for mobile and web applications. An attacker can update a user account without proper authorization checks, allowing them to discover whether email addresses or usernames exist in the system and potentially confirm passwords before they're locked out, even without a valid login session.

Technologies: Parse Community Parse Server. Vendors: Parse Community.

Quick answers

Is CVE-2026-112768 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-112768 being exploited in the wild.
How severe is CVE-2026-112768?
Informational severity, published 19 October 2026.
Which products and versions are affected?
Parse Community Parse Server 8.0.0 to before 8.6.99; 9.0.0 to before 9.10.3-alpha.2.
Is there a fix for CVE-2026-112768?
Yes: fixed in Parse Server 8.6.99, 9.10.3-alpha.2. Until then: Remove the Parse Server options passwordPolicy.maxPasswordHistory and passwordPolicy.doNotAllowUsername to prevent disclosure of password information, though this does not fully mitigate the username and email enumeration aspects of the vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112768 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-112768?
Check whether you run Parse Community Parse Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Parse Server 8.6.99, 9.10.3-alpha.2

Remove the Parse Server options passwordPolicy.maxPasswordHistory and passwordPolicy.doNotAllowUsername to prevent disclosure of password information, though this does not fully mitigate the username and email enumeration aspects of the vulnerability.

Technical details

The vulnerability occurs because Parse Server performs validation checks against the target user account during an update operation before verifying that the caller is authorized to perform that update. An unauthenticated or unauthorized attacker can craft user update requests that leak information about existing accounts through response timing or content. When password policies like maxPasswordHistory or doNotAllowUsername are enabled, the attacker can additionally confirm guessed passwords or detect whether a password contains the username.

Affected products

  • Parse Community Parse Server 8.0.0 to before 8.6.99; 9.0.0 to before 9.10.3-alpha.2

Timeline

  • 2026-10-05: disclosed: GitHub security advisory GHSA-p49q-9w65-f9p7 published
  • 2026-10-19: advisory: CVE-2026-112768 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.