CVE-2026-123487

waiting for further signalsZero needs more public information before it can validate it.

GHSA-r7pw-r949-xvmf ↗EUVD-2026-118287 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
parse-community parse-server >= 9.0.0, < 9.10.7-alpha.1; < 8.6.115
fixed in 9.10.7-alpha.1, 8.6.115
CWE-1333 Inefficient Regular Expression Complexity
ETK-2026-3730Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 08h 56msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h13m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Parse Server releases before 8.6.115, and 9.x releases before 9.10.7-alpha.1, are affected by inefficient email-address validation. An attacker can cause event-loop starvation and disrupt service through registration or email-update requests; registration requires the application ID, while email updates require an account.

mitigation

Upgrade Parse Server to 8.6.115 or later, or to 9.10.7-alpha.1 or later for the 9.x line. Restrict access to registration and email-update endpoints where feasible until upgrades are complete.

fixed in 9.10.7-alpha.1, 8.6.115

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 15:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-06 15:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-123487

{
  "etk_id": "ETK-2026-3730",
  "cve_id": "CVE-2026-123487",
  "display_id": "CVE-2026-123487",
  "ghsa_id": "GHSA-r7pw-r949-xvmf",
  "euvd_id": "EUVD-2026-118287",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic regex denial of service in Parse Server",
  "summary": "Parse Server releases before 8.6.115, and 9.x releases before 9.10.7-alpha.1, are affected by inefficient email-address validation. An attacker can cause event-loop starvation and disrupt service through registration or email-update requests; registration requires the application ID, while email updates require an account.",
  "mitigation": "Upgrade Parse Server to 8.6.115 or later, or to 9.10.7-alpha.1 or later for the 9.x line. Restrict access to registration and email-update endpoints where feasible until upgrades are complete.",
  "vendor": "parse-community",
  "product": "parse-server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.0.0, < 9.10.7-alpha.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "9.10.7-alpha.1"
      ],
      "package_name": "parse-server",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 8.6.115"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "8.6.115"
      ],
      "package_name": "parse-server",
      "purl": null
    }
  ],
  "cwes": [
    1333
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.971838533333333,
  "t0_at": "2026-11-06T15:00:49.384000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T15:00:49.384000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T15:00:49.384000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123487"
    }
  }
}

published 2026-11-06 15:21Z
last change 2026-11-07 10:16Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.