CVE-2026-50008

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 74% 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. From version 9.8.0 to before version 9.9.1-alpha.3, the routeAllowList server option restricts external client access to a configured list of REST API routes. The check is only enforced as Express middleware against the outer HTTP request URL, so the /batch handler dispatches each sub-request to the internal router without re-running the allow-list check. An external caller whose outer route matches batch can issue batch sub-requests to any REST API route that the operator omitted from the allow-list. Authentication, ACL, CLP, and other inner-route authorization controls still apply — only the operator-configured route firewall is bypassed. This issue has been patched in version 9.9.1-alpha.3.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
—
EPSS
26.7%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (2)

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

Server option routeAllowList is bypassable through batch sub-requests · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-p84r-h6rx-f2xr
github_pr Patch Available

fix: Server option routeAllowList is bypassable through batch sub-requests (GHSA-p84r-h6rx-f2xr)

Patch available: parse-community/parse-server 9.9.1-alpha.3 (PR #10482 merged 2026-05-27)

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

Vendor Advisories for CVE-2026-50008(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—9.9.1-alpha.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 32 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-29 14:06 UTCEPSS rescore
  5. 2026-06-29 14:06 UTCEPSS rescore
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-21 01:59 UTCEPSS rescore
  20. 2026-06-19 19:26 UTCEPSS rescore
  21. 2026-06-19 19:26 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-17 17:53 UTCEPSS rescore
  25. 2026-06-16 17:53 UTCEPSS rescore
  26. 2026-06-15 17:49 UTCEPSS rescore
  27. 2026-06-15 17:49 UTCEPSS rescore
  28. 2026-06-14 23:18 UTCEPSS rescore
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 20:13 UTCEG score recompute
  32. 2026-06-12 20:13 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50008?
CVE-2026-50008 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. From version 9.8.0 to before version 9.9.1-alpha.3, the routeAllowList server option restricts external client access to a configured list of REST API routes. The check is only enforced as…
When was CVE-2026-50008 disclosed?
CVE-2026-50008 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-50008 actively exploited?
CVE-2026-50008 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50008?
CVE-2026-50008 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-50008?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50008, 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-50008

Explore →

Is Your Infrastructure Affected by CVE-2026-50008?

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

Start Free Scan →Browse All CVEs