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

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

GHSA-vg7p-vv4q-4272 ↗

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 ae55300
fixed in commits 7f76f0d and above
ETK-2026-2554Zero's internal tracking ID, independent of the CVE number., no cve assigned
4h 29msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −38h08mwaiting for further signals−4h29m
−36h
−24h
−12h
0

description

H2O may access released request state when a deferred error timer executes after an HTTP/2 stream has been reset. Exposure requires reproxy or error-document handling that can generate an invalid delegated redirect, along with an attacker able to reset an HTTP/2 stream.

mitigation

Upgrade h2o to commits 7f76f0d and above or later.

fixed in commits 7f76f0d 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
19m
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:55Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2554",
  "cve_id": null,
  "display_id": "ETK-2026-2554",
  "ghsa_id": "GHSA-vg7p-vv4q-4272",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "HTTP/2 deferred timer use-after-free in H2O",
  "summary": "H2O may access released request state when a deferred error timer executes after an HTTP/2 stream has been reset. Exposure requires reproxy or error-document handling that can generate an invalid delegated redirect, along with an attacker able to reset an HTTP/2 stream.",
  "mitigation": "Upgrade h2o to commits 7f76f0d and above or later.",
  "vendor": "other",
  "product": "other:h2o",
  "affected": [
    {
      "affected_notes": [
        "commits up to ae55300"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "commits 7f76f0d 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": 19.32968245,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-23T08:55:43+00:00",
      "days": -1.5886672316087962,
      "is_lower_bound": true,
      "measured_at": "2026-10-24T23:03:23.874541+00:00",
      "url": "https://github.com/h2o/h2o/security/advisories/GHSA-vg7p-vv4q-4272"
    }
  }
}

published 2026-10-24 17:16Z
last change 2026-10-24 23:00Z

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.