CVE-2026-115823

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

GHSA-4q75-5w63-6hx7 ↗EUVD-2026-109560 ↗

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-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
ETK-2026-2616Zero's internal tracking ID, independent of the CVE number., permanent identifier
6h 04msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h42m
0
+2h
+6h
+8h
+10h
+12h

description

Starman versions before 0.4019 can emit response content for HEAD and other bodyless HTTP responses, causing persistent connections to become misaligned. An attacker may cause a front-end proxy that reuses upstream connections to associate responses with the wrong requests. The issue requires keep-alive or pipelined connections and an affected response path.

mitigation

Upgrade Starman to version 0.4019 or later. Until upgraded, reduce exposure by disabling or limiting reuse of persistent upstream connections through front-end proxies.

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
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-25 16:51Z
Δ 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:51Z
    ghsa: trigger signal, started the run
  2. 2026-10-25 16:51Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2616",
  "cve_id": "CVE-2026-115823",
  "display_id": "CVE-2026-115823",
  "ghsa_id": "GHSA-4q75-5w63-6hx7",
  "euvd_id": "EUVD-2026-109560",
  "status": "published",
  "anchor_state": "anchored",
  "title": "HTTP response desynchronization in Starman",
  "summary": "Starman versions before 0.4019 can emit response content for HEAD and other bodyless HTTP responses, causing persistent connections to become misaligned. An attacker may cause a front-end proxy that reuses upstream connections to associate responses with the wrong requests. The issue requires keep-alive or pipelined connections and an affected response path.",
  "mitigation": "Upgrade Starman to version 0.4019 or later. Until upgraded, reduce exposure by disabling or limiting reuse of persistent upstream connections through front-end proxies.",
  "vendor": null,
  "product": "Starman",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.4019"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.4019"
      ],
      "package_name": "Starman",
      "purl": null
    }
  ],
  "cwes": [
    444
  ],
  "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": 15.0467093,
  "t0_at": "2026-10-25T16:51:19.961000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T16:51:19.961000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T16:51:19.961000+00:00",
      "url": "https://github.com/advisories/GHSA-4q75-5w63-6hx7"
    }
  }
}

published 2026-10-25 20:18Z
last change 2026-10-26 02:23Z

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.