Skip to content
Web

CVE-2026-123487

8.7
High
EPSS n/aPatch available

ReDoS via email regex in Parse Server causing Node.js event-loop DoS

exploited
No known exploitation not in CISA KEV as of our last sync
fix
Fixed in 9.10.7-alpha.1, 8.6.115
likelihood
No EPSS score yet
Published 6 Nov 2026Analysed here 7 Nov 2026CVSS scored by the publisher (CNA)

do firstUpgrade to a fixed release: 9.10.7-alpha.1, 8.6.115.

common questions

Is CVE-2026-123487 being exploited?

Not confirmed. CVE-2026-123487 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-123487?

CVE-2026-123487 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-123487?

Yes. A fix has been recorded for CVE-2026-123487. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-123487 affect?

CVE-2026-123487 affects Parse Server < 8.6.115, Parse Server 9.0.0 < 9.10.7-alpha.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-123487?

Upgrade to 8.6.115 or 9.10.7-alpha.1+; enforce email length limits and rate-limit signups/WAF rules.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Parse Server < 8.6.115Parse Server 9.0.0 < 9.10.7-alpha.1
impact

Unauthenticated or authenticated attacker can submit a long crafted email to trigger regex ReDoS, block the Node.js event loop, and cause service denial.

action required

Patch when possible

affected versions
parse-community parse-server
  • affected>= 9.0.0 and < 9.10.7-alpha.1
  • affected< 8.6.115
vendor says fixed in9.10.7-alpha.1, 8.6.115

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
none
automatable
yes
technical impact
partial

Assessed by CISA 6 Nov 2026 (SSVC 2.0.3).

timeline

  1. 6 Nov 2026Published
  2. 6 Nov 2026CISA SSVC assessment: exploitation none · same day later
  3. 6 Nov 2026CVE record last updated · same day later
  4. 7 Nov 2026Analysed by vulneraibility.com · 1 day later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 advisories
  • Advisorygithub.com /parse-community/parse-server/security/advisories/GHSA-9492-427f-466x
  • Advisoryvulncheck.com /advisories/parse-server-9.0.0-before-9.10.7-alpha.1-redos-via-email-validation-

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • OSV: advisory aliases and downstream package versions
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved