CVE-2026-115817

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

GHSA-xcqf-6xfj-3q3x ↗EUVD-2026-109558 ↗

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.
Starman < 0.4019
fixed in 0.4019
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-2606Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 54msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h34m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Starman versions earlier than 0.4019 can leave request-processing workers occupied while an HTTP request body remains incomplete. A remote client that can keep such connections open may exhaust the available workers and disrupt service; the condition requires requests with completed headers but an unfinished body.

mitigation

Upgrade Starman to version 0.4019 or later. After upgrading, review and set the body timeout to a value appropriate for expected request sizes and client behavior.

fixed in 0.4019

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-25 16:50Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-25 16:50Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2606",
  "cve_id": "CVE-2026-115817",
  "display_id": "CVE-2026-115817",
  "ghsa_id": "GHSA-xcqf-6xfj-3q3x",
  "euvd_id": "EUVD-2026-109558",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Request-body timeout denial of service in Starman",
  "summary": "Starman versions earlier than 0.4019 can leave request-processing workers occupied while an HTTP request body remains incomplete. A remote client that can keep such connections open may exhaust the available workers and disrupt service; the condition requires requests with completed headers but an unfinished body.",
  "mitigation": "Upgrade Starman to version 0.4019 or later. After upgrading, review and set the body timeout to a value appropriate for expected request sizes and client behavior.",
  "vendor": null,
  "product": "Starman",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.4019"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.4019"
      ],
      "package_name": "Starman",
      "purl": null
    }
  ],
  "cwes": [
    770
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.633391483333334,
  "t0_at": "2026-10-25T16:50:33.914000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T16:50:33.914000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T16:50:33.914000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115817"
    }
  }
}

published 2026-10-25 17:23Z
last change 2026-10-25 21:01Z

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.