CVE-2026-116161: Parse Server 9.0.0 before 9.10.5 LiveQuery Information Disclosure via $or Subscriptions

Published Oct 25, 2026
·
Updated

Parse Server before 8.6.103 and 9.0.0 before 9.10.5 contains an information disclosure vulnerability in LiveQuery. Its subscription hash omits constraints next to a $or operator, including the Session owner filter and beforeSubscribe constraints, so distinct subscriptions are grouped together. Authenticated clients subscribing with $or queries can receive other users' events, including session tokens usable for impersonation.

Other sources

Parse Server before 8.6.103 and 9.0.0 before 9.10.5-alpha.4 contains an information disclosure vulnerability in LiveQuery. Its subscription hash omits constraints next to a $or operator, including the Session owner filter and beforeSubscribe constraints, so distinct subscriptions are grouped together. Authenticated clients subscribing with $or queries can receive other users' events, including session tokens usable for impersonation.

— MITRE

Affected Software

3 affected componentsFixes available
Parse Parse Server<8.6.103, >=9.0.0<9.10.5-alpha.4
bitnami/parse<8.6.103
8.6.103
bitnami/parse>=9.0.0<9.10.5
9.10.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade bitnami/parse to a version that resolves this vulnerability.

    Fixed in 8.6.103
  2. Upgrade

    Upgrade bitnami/parse to a version that resolves this vulnerability.

    Fixed in 9.10.5

Event History

Oct 25, 2026
CVE Published
via MITRE·01:20 PM
Data Sourced
via MITRE·01:20 PM
DescriptionWeakness
Data Sourced
via OSV·01:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Oct 30, 2026
Advisory Published
via OSV·03:35 PM
Data Sourced
via OSV·03:35 PM
Affected Software

Frequently Asked Questions

1

Which deployments are affected?

Parse Server versions before 8.6.103 are affected, as are versions from 9.0.0 through before 9.10.5-alpha.4. The issue is in LiveQuery subscription handling.

2

What does an attacker need to exploit this issue?

An attacker needs to be an authenticated client and create a LiveQuery subscription using a query with a $or operator. Under those conditions, distinct subscriptions can be grouped together.

3

What information could be exposed?

Affected clients can receive events belonging to other users. Exposed events may include session tokens that can be used to impersonate those users.

4

Are authorization-related LiveQuery restrictions bypassed?

Yes. The omitted subscription-hash constraints include the _Session owner filter and beforeSubscribe constraints, allowing subscriptions with distinct restrictions to be grouped together.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203