ETK-2026-2553Zero's internal tracking ID, independent of the CVE number.

validatedZero produced an exploit or a check.

GHSA-8628-6j2f-ppm9 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:h2o commits up to d21e7cb
fixed in commits a60aea4 and above
ETK-2026-2553Zero's internal tracking ID, independent of the CVE number., no cve assigned
−5h22mTTV
25mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org, not yet published
trigger signal −37h50mcheck available−5h22magent stopped
−36h
−24h
−12h
0

description

h2o's compressed static-file variant handling can write past a heap buffer. A remote client advertising Zstd support can crash a worker when file.send-compressed is enabled.

mitigation

Upgrade h2o to commits a60aea4 and above or later.

fixed in commits a60aea4 and above

check
available
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.
deterministic
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
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-23 08:58Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2553

{
  "etk_id": "ETK-2026-2553",
  "cve_id": null,
  "display_id": "ETK-2026-2553",
  "ghsa_id": "GHSA-8628-6j2f-ppm9",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Heap buffer overflow in h2o static-file compression handling",
  "summary": "h2o's compressed static-file variant handling can write past a heap buffer. A remote client advertising Zstd support can crash a worker when `file.send-compressed` is enabled.",
  "mitigation": "Upgrade h2o to commits a60aea4 and above or later.",
  "vendor": "other",
  "product": "other:h2o",
  "affected": [
    {
      "affected_notes": [
        "commits up to d21e7cb"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "commits a60aea4 and above"
      ],
      "package_name": "h2o",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 24.627988816666665,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-24T17:27:27.167798+00:00",
      "days": -0.22344157537037038,
      "is_lower_bound": true,
      "measured_at": "2026-10-24T22:49:12.579037+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-23T08:58:54+00:00",
      "days": -1.5766032396990741,
      "is_lower_bound": true,
      "measured_at": "2026-10-24T22:49:12.579037+00:00",
      "url": "https://github.com/h2o/h2o/security/advisories/GHSA-8628-6j2f-ppm9"
    }
  }
}

published 2026-10-24 17:02Z
last change 2026-10-24 22:27Z

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.