Skip to main content
CVE-2026-116161VulnerabilityPublished 10/25/2026

CVE-2026-116161: parse-server · Information Exposure

Affects parse-community parse-serverSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium · fixed in 8.6.103 : update parse-community parse-server when convenient.

Data as of 10/25/2026, 17:13:39 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 8.6.103
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
parse-communityparse-serverAffected
  • >=9.0.0 <9.10.5-alpha.4
Fixed in
  • 9.10.5-alpha.4
parse-communityparse-serverAffected
  • <8.6.103
Fixed in
  • 8.6.103
GitHubparse-community/parse-serverpkg:github/parse-community/parse-serverOther threatsAffected
  • <8.6.103
  • >=9.0.0 <9.10.5-alpha.4
Fixed in
  • 8.6.103
  • 9.10.5-alpha.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in parse-server versions 8.6.103 and 9.10.5-alpha.4 and later. Users should upgrade to these or later versions to remediate the vulnerability. There is no indication that temporary mitigations or workarounds are provided, so applying the official fix is recommended.

Description

Parse Server versions before 8.6.103 and 9.0.0 before 9.10.5-alpha.4 have an information disclosure vulnerability in the LiveQuery feature. The vulnerability arises because the subscription hash does not include constraints adjacent to a $or operator, such as the _Session owner filter and beforeSubscribe constraints. This causes distinct subscriptions to be grouped together, allowing authenticated clients using $or queries to receive events intended for other users, including session tokens that could be used for impersonation.

Impact

Authenticated clients can receive events belonging to other users, including session tokens. This exposure of sensitive information can lead to impersonation of other users within the system. The vulnerability compromises user session confidentiality and could facilitate unauthorized access.

References

Community reviews

Loading reviews…