CVE-2026-44453: Prior to commit 6b5370d, h2o is vulnerable to a Denial of Service attack when calling alloca under
Affects h2oSource GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 17 Nov 2026, 06:51 UTC
CVSS:3.1/AV:N/AC:L/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 6b5370d. Users should upgrade to a version of h2o that includes this commit to remediate the issue. No other mitigation or workaround is indicated.
Description
h2o HTTP server versions prior to commit 6b5370d are vulnerable to a Denial of Service (DoS) condition caused by excessive stack memory allocation using alloca when serving static files. This can lead to a crash due to stack overflow and segmentation fault. The issue has been fixed in commit 6b5370d.