Medium

CVE-2026-116801 — Parse Server 9.0.0 before 9.10.5-alpha.6 ACL Bypass via $relatedTo Query

Parse Server before 8.6.105 and 9.0.0 before 9.10.5-alpha.6 does not validate the owning object reference in $relatedTo relation queries, so supplying a query operator instead of an object ID bypasses the owning-object ACL check. A client with read access to at least one object of the owning class can disclose which readable objects are linked to owning objects it cannot read.

Published Oct 26, 2026 · Updated Oct 26, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Parse-community

Parse-server

CVSS base

4.3

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Parse-community Parse-server).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Parse-community	Parse-server	≥ 9.0.0 and < 9.10.5-alpha.6< 8.6.105	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.3	CVSS 4.0	Medium	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
5.3	CVSS 4.0	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
4.3	CVSS 3.1	Medium	2.8	1.4	disclosure@vulncheck.com via NIST National Vulnerability Database
4.3	CVSS 3.1	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-943

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · parse-community/parse-server
Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 26, 2026
CVSS changed · 4.3
Oct 26, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 26, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 26, 2026 · Alertas do Telegram
CVE published
Oct 26, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 26, 2026 – Oct 26, 2026
1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

2 on the record

github.com/parse-community/parse-server/security/advisories/GHSA-58m4-cqvw-4vgh
vendor-advisory, NIST National Vulnerability Database
www.vulncheck.com/advisories/parse-server-9.0.0-before-9.10.5-alpha.6-acl-bypass-via-re
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Parse-community
every CVE for this vendor

CWE-943
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-116165 Parse Server 9.0.0 before 9.10.4-alpha.4 Unauthenticated Class Schema Deletion on MongoDB 1d
Medium CVE-2026-116164 Parse Server 9.0.0 before 9.10.4-alpha.3 Reserved Field Name Injection via Object Writes 1d
High CVE-2026-116163 Parse Server 9.0.0 before 9.10.5-alpha.2 Authentication Bypass via AuthAdapter Subclasses 1d
Low CVE-2026-116162 Parse Server 9.0.0 before 9.10.5-alpha.5 Privilege Escalation via SMS MFA Login 1d
Medium CVE-2026-116161 Parse Server 9.0.0 before 9.10.5-alpha.4 LiveQuery Information Disclosure via $or Subscriptions 1d
Low CVE-2026-112769 Parse Server before 8.6.98 and 9.x before 9.10.3-alpha.1 Session Class-Level Permission Bypass 7d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-116801 is "Parse Server 9.0.0 before 9.10.5-alpha.6 ACL Bypass via $relatedTo Query", rated Medium. It affects Parse-server (Parse-community); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.