CVE-2026-53726

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.80 and 9.9.1-alpha.6, a relation query using the $relatedTo operator could read the membership of a Relation field even when that field was hidden from the requesting client by protectedFields, and even when the object owning the relation was not readable by the client under its ACL or class-level permissions. The request requires only the public API credentials that Parse clients normally carry — no user session, master key, or Cloud Code is needed. As a result, an unauthenticated client who knows or obtains the owning object's objectId could enumerate the objects linked through a protected relation, or combine the operator with an objectId constraint to use it as a membership oracle — confirming whether a specific object is linked to a private parent. This affects applications that rely on protectedFields or object ACLs to keep Relation membership confidential, such as private group memberships, block lists, or account-to-resource associations. This issue has been patched in versions 8.6.80 and 9.9.1-alpha.6.

CVSS v3
6.9
EG Score
6.9(medium)
EPSS
19.4%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: github_pr, github.
github Patch Available

Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-wmwx-jr2p-4j4r
github_pr Patch Available

fix: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL (GHSA-wmwx-jr2p-4j4r)

Patch available: parse-community/parse-server 8.6.80 (PR #10494 merged 2026-06-03)

https://github.com/parse-community/parse-server/pull/10494
github_pr Patch Available

fix: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL (GHSA-wmwx-jr2p-4j4r)

Patch available: parse-community/parse-server 9.9.1-alpha.6 (PR #10493 merged 2026-06-03)

https://github.com/parse-community/parse-server/pull/10493

Vendor Advisories for CVE-2026-53726(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
parse-server—8.6.80—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 05:06 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 03:43 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-05 01:47 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 00:03 UTCEG score recompute
  13. 2026-07-02 22:42 UTCEG score recompute
  14. 2026-07-01 21:23 UTCEG score recompute
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 20:03 UTCEG score recompute
  18. 2026-06-29 18:42 UTCEG score recompute
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 16:57 UTCEG score recompute
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 15:37 UTCEG score recompute
Show 37 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 14:18 UTCEG score recompute
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-25 12:47 UTCEG score recompute
  5. 2026-06-24 14:05 UTCEPSS rescore
  6. 2026-06-24 11:28 UTCEG score recompute
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 10:08 UTCEG score recompute
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-22 08:48 UTCEG score recompute
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 14:56 UTCEPSS rescore
  15. 2026-06-21 07:26 UTCEG score recompute
  16. 2026-06-21 01:59 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-20 05:59 UTCEG score recompute
  19. 2026-06-19 19:26 UTCEPSS rescore
  20. 2026-06-19 19:26 UTCEPSS rescore
  21. 2026-06-19 04:20 UTCEG score recompute
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 02:51 UTCEG score recompute
  25. 2026-06-17 17:53 UTCEPSS rescore
  26. 2026-06-17 01:31 UTCEG score recompute
  27. 2026-06-16 17:53 UTCEPSS rescore
  28. 2026-06-16 00:12 UTCEG score recompute
  29. 2026-06-15 17:49 UTCEPSS rescore
  30. 2026-06-15 17:49 UTCEPSS rescore
  31. 2026-06-14 23:18 UTCEPSS rescore
  32. 2026-06-14 22:52 UTCEG score recompute
  33. 2026-06-13 23:00 UTCEPSS rescore
  34. 2026-06-13 21:33 UTCEG score recompute
  35. 2026-06-12 23:12 UTCEPSS rescore
  36. 2026-06-12 20:13 UTCEG score recompute
  37. 2026-06-12 20:13 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53726?
CVE-2026-53726 is a medium vulnerability published on June 12, 2026. Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.80 and 9.9.1-alpha.6, a relation query using the $relatedTo operator could read the membership of a Relation field even when that field was hidden from the requesting client…
When was CVE-2026-53726 disclosed?
CVE-2026-53726 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53726 actively exploited?
CVE-2026-53726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53726?
CVE-2026-53726 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-53726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53726, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53726

Explore →

Is Your Infrastructure Affected by CVE-2026-53726?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs