Is CVE-2026-116162 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116162 being exploited in the wild.

How severe is CVE-2026-116162?

Informational severity, published 25 October 2026.

Which products and versions are affected?

Parse Community Parse Server 8.0.0 before 8.6.104; 9.0.0 before 9.10.5-alpha.5.

How is CVE-2026-116162 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-116162?

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.

CVE-2026-116162: Parse Server privilege escalation via SMS MFA login

CVE-2026-116162 · Severity: info · Published 2026-10-25

Parse Server is a backend platform that provides user authentication and data management for mobile and web applications. When SMS-based multi-factor authentication is enabled, a user enrolled in SMS MFA can inject extra fields into a login verification request to modify their own account settings that normally require administrative access, such as email verification status or fields protected by authentication rules. This allows an authenticated user to bypass security restrictions on their own account.

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

Quick answers

Is CVE-2026-116162 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116162 being exploited in the wild.
How severe is CVE-2026-116162?: Informational severity, published 25 October 2026.
Which products and versions are affected?: Parse Community Parse Server 8.0.0 before 8.6.104; 9.0.0 before 9.10.5-alpha.5.
Is there a fix for CVE-2026-116162?: Yes: fixed in Parse Server 8.6.104, 9.10.5-alpha.5. Until then: Deployments that do not enable SMS-based MFA are unaffected. For deployments using SMS MFA, upgrading to a patched release is required as there is no configuration workaround.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-11"},{"kind":"advisory","at":"2026-10-25"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116162 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-116162?: 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.104, 9.10.5-alpha.5

Deployments that do not enable SMS-based MFA are unaffected. For deployments using SMS MFA, upgrading to a patched release is required as there is no configuration workaround.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-11"},{"kind":"advisory","at":"2026-10-25"}]

Technical details

The vulnerability exists in Parse Server's SMS MFA verification-code request handler, which persists the entire incoming login request using master-key privileges instead of only the authentication data needed for the one-time token. An SMS MFA-enrolled user can include additional fields (e.g., emailVerified flag, beforeSave-protected values) in the verification request to modify their own account record, bypassing client-level write restrictions. The issue requires the attacker to already have valid credentials and SMS MFA enrollment on their own account; it does not allow modification of other users' data.

Affected products

Parse Community Parse Server 8.0.0 before 8.6.104; 9.0.0 before 9.10.5-alpha.5

References

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