Threat Intelligence Database

H3 is a minimal H(TTP) framework. In versions 2.0.0-0 through 2.0.1-rc.16, the `mount()` method in h3 uses a simple `startsWith()` check to determine whether incoming requests fall under a mounted sub-application's path prefix. Because this check does not verify a path segment boundary (i.e., that the next character after the base is `/` or end-of-string), middleware registered on a mount like `/admin` will also execute for unrelated routes such as `/admin-public`, `/administrator`, or `/adminstuff`. This allows an attacker to trigger context-setting middleware on paths it was never intended to cover, potentially polluting request context with unintended privilege flags. Version 2.0.2-rc.17 contains a patch.

LowVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33490#cwe-706

CVE-2026-33129 is a timing side-channel vulnerability in the h3js framework versions 2.0.1-beta.0 through 2.0.0-rc.8. The flaw exists in the requireBasicAuth function due to unsafe string comparison using ! ==, allowing attackers to measure response times and deduce valid password characters sequentially. This bypasses password complexity protections without requiring authentication or user interaction.

MediumVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33129#cwe-208

H3 is a minimal H(TTP) framework. In versions prior to 1.15.6 and between 2.0.0 through 2.0.1-rc.14, createEventStream is vulnerable to Server-Sent Events (SSE) injection due to missing newline sanitization in formatEventStreamMessage() and formatEventStreamComment(). An attacker who controls any part of an SSE message field (id, event, data, or comment) can inject arbitrary SSE events to connected clients. This issue is fixed in versions 1.15.6 and 2.0.1-rc.15.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33128#cwe-93

H3 is a minimal H(TTP) framework built for high performance and portability. Prior to 1.15.5, there is a critical HTTP Request Smuggling vulnerability.readRawBody is doing a strict case-sensitive check for the Transfer-Encoding header. It explicitly looks for "chunked", but per the RFC, this header should be case-insensitive. This vulnerability is fixed in 1.15.5.