Unauthenticated server crash via stack path allocation
Published Jul 16, 2026 · Updated Jul 16, 2026
Stack exhaustion in H2O before commit 6b5370d allows remote attackers to crash the HTTP server via crafted static-file requests. The static-file handler's on_req path builder sizes an alloca buffer from the configured real path, normalized request path, and index name. Exploitation requires a musl-based deployment whose pthread stack is smaller than the resulting allocation; the resulting guard-page fault terminates the server process.
Summary
What happened
Stack exhaustion in H2O before commit 6b5370d allows remote attackers to crash the HTTP server via crafted static-file requests. The static-file handler's on_req path builder sizes an alloca buffer from the configured real path, normalized request path, and index name. Exploitation requires a musl-based deployment whose pthread stack is smaller than the resulting allocation; the resulting guard-page fault terminates the server process.
The record
- CVE
- CVE-2026-44453
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- H2O Project
- Product
- H2O
- Classifications
- CWE-789, CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6b5370d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo