CVE-2026-55368

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

GHSA-m998-r5ww-rqjf ↗

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 4212ce1
fixed in commits 48b7ae1 and above
ETK-2026-2550Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 16msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+32h33m
0
+12h
+24h
+36h

description

H2O instances using custom access-log formats are affected by an out-of-bounds write in the access-log formatter. A request reaching an affected formatting path can crash the server; impact beyond a crash has not been established.

mitigation

Upgrade h2o to commits 48b7ae1 and above or later.

fixed in commits 48b7ae1 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.
contextual
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
17m
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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2550",
  "cve_id": "CVE-2026-55368",
  "display_id": "CVE-2026-55368",
  "ghsa_id": "GHSA-m998-r5ww-rqjf",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Out-of-bounds write in H2O access-log formatting",
  "summary": "H2O instances using custom access-log formats are affected by an out-of-bounds write in the access-log formatter. A request reaching an affected formatting path can crash the server; impact beyond a crash has not been established.",
  "mitigation": "Upgrade h2o to commits 48b7ae1 and above or later.",
  "vendor": "other",
  "product": "other:h2o",
  "affected": [
    {
      "affected_notes": [
        "commits up to 4212ce1"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "commits 48b7ae1 and above"
      ],
      "package_name": "h2o",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.11939875,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-23T08:26:14+00:00",
      "days": -1.575659667523148,
      "is_lower_bound": true,
      "measured_at": "2026-10-24T22:15:11.054519+00:00",
      "url": "https://github.com/h2o/h2o/security/advisories/GHSA-m998-r5ww-rqjf"
    }
  }
}

published 2026-10-24 16:45Z
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.