Quick answers
- Is CVE-2026-53726 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53726 being exploited in the wild.
- How severe is CVE-2026-53726?
- Medium severity, with a CVSS score of 4, published 12 June 2026.
- Which products and versions are affected?
- parse-server (npm) SEMVER:introduced=9.0.0,fixed=9.9.1-alpha.6.
- Is there a fix for CVE-2026-53726?
- Yes. parse-server (npm): upgrade to 9.9.1-alpha.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53726 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53726?
- Check whether you run parse-server (npm) 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
- parse-server (npm): upgrade to 9.9.1-alpha.6 or later
npm install parse-server@9.9.1-alpha.6
Technical details
A vulnerability in the `$relatedTo` query operator allows for an authorization bypass (CWE-639). The root cause is that the relation query path failed to validate the caller's authentication context against the owning object's ACLs or the class's `protectedFields` before querying the join table. An unauthenticated attacker with knowledge of a target `objectId` can use this to enumerate linked objects or perform a membership oracle attack to confirm if a specific object is linked to a private parent. The issue is fixed in versions 8.6.80 and 9.9.1-alpha.6 by enforcing authorization checks on the owning object and its fields before returning results.
Affected products
- Parse Community parse-server >= 9.0.0, < 9.9.1-alpha.6; < 8.6.80
Identifiers
- CVE-2026-53726
- GHSA-wmwx-jr2p-4j4r
Timeline
- 2026-06-04: disclosed: Initial disclosure to the vendor
- 2026-06-12: advisory: NVD publication date
- 2026-06-19: advisory: GitHub Advisory published