CVE-2026-115822

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

GHSA-2826-qw6w-9h42 ↗EUVD-2026-109559 ↗

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-1333 Inefficient Regular Expression Complexity
ETK-2026-2607Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 25msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h02m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Starman versions earlier than 0.4019 can spend excessive CPU processing malformed chunked HTTP request bodies. A remote party able to send requests to the service may tie up worker capacity before the application handles the request.

mitigation

Upgrade Starman to version 0.4019 or later. Until upgraded, restrict untrusted access to the service and enforce request-size limits at a reverse proxy where possible.

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.
contextual
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
29m
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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2607",
  "cve_id": "CVE-2026-115822",
  "display_id": "CVE-2026-115822",
  "ghsa_id": "GHSA-2826-qw6w-9h42",
  "euvd_id": "EUVD-2026-109559",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic regex backtracking CPU exhaustion in Starman",
  "summary": "Starman versions earlier than 0.4019 can spend excessive CPU processing malformed chunked HTTP request bodies. A remote party able to send requests to the service may tie up worker capacity before the application handles the request.",
  "mitigation": "Upgrade Starman to version 0.4019 or later. Until upgraded, restrict untrusted access to the service and enforce request-size limits at a reverse proxy where possible.",
  "vendor": null,
  "product": "Starman",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.4019"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.4019"
      ],
      "package_name": "Starman",
      "purl": null
    }
  ],
  "cwes": [
    1333
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.528517866666668,
  "t0_at": "2026-10-25T16:51:00.241000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T16:51:00.241000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T16:51:00.241000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115822"
    }
  }
}

published 2026-10-25 17:24Z
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.