Prior to commit 8dc37cb, when h2o receives a ClientHello message over TLS or QUIC and it contains a zero-length SNI
Affects h2oSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium.
Data as of 17 Nov 2026, 06:51 UTC
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSh2opkg:deb/ubuntu/h2o?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSdnsdistpkg:deb/ubuntu/dnsdist?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSh2opkg:deb/ubuntu/h2o?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSh2opkg:deb/ubuntu/h2o?arch=source&distro=esm-apps/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSh2opkg:deb/ubuntu/h2o?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability has been fixed by commit 8dc37cb. Users should upgrade to a version of h2o that includes this commit to remediate the issue. No additional mitigations are indicated.
Description
A vulnerability in h2o HTTP server prior to commit 8dc37cb allows a denial-of-service condition when processing a TLS or QUIC ClientHello message containing a zero-length Server Name Indication (SNI) extension. The server incorrectly handles the zero-length hostname, potentially causing a segmentation violation and crash. This issue has been fixed in commit 8dc37cb.