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

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

GHSA-48jv-5969-gjg3 ↗

no check availablenot proven exploitable
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 fd8d69e
fixed in commits 3d47065 and above
ETK-2026-2556Zero's internal tracking ID, independent of the CVE number., no cve assigned
4h 18msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+32h57m
0
+12h
+24h
+36h

description

H2O's HTTP/2 Cache-Digest handling can retain excessive decoded data while request streams remain open. An unauthenticated remote client can exhaust server memory and terminate the process. The affected path is enabled by the default HTTP/2 configuration and does not depend on server push.

mitigation

Upgrade h2o to commits 3d47065 and above or later.

fixed in commits 3d47065 and above

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.
no
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.
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

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-23 08:53Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2556",
  "cve_id": null,
  "display_id": "ETK-2026-2556",
  "ghsa_id": "GHSA-48jv-5969-gjg3",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cache-Digest memory exhaustion in H2O HTTP/2",
  "summary": "H2O's HTTP/2 Cache-Digest handling can retain excessive decoded data while request streams remain open. An unauthenticated remote client can exhaust server memory and terminate the process. The affected path is enabled by the default HTTP/2 configuration and does not depend on server push.",
  "mitigation": "Upgrade h2o to commits 3d47065 and above or later.",
  "vendor": "other",
  "product": "other:h2o",
  "affected": [
    {
      "affected_notes": [
        "commits up to fd8d69e"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "commits 3d47065 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": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.70713735,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-23T08:53:49+00:00",
      "days": -1.5517026226041668,
      "is_lower_bound": true,
      "measured_at": "2026-10-24T22:08:16.270417+00:00",
      "url": "https://github.com/h2o/h2o/security/advisories/GHSA-48jv-5969-gjg3"
    }
  }
}

published 2026-10-24 17:31Z
last change 2026-10-24 21:56Z

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.