Skip to content

CVE-2026-33490 h3: Missing Path Segment Boundary Check in `mount()` Causes Middleware Execution on Unrelated Prefix-Matching Routes

MediumCVSS 5.3 EPSS 0.25%
Published
Updated
Exploit status
No public exploit known

Description

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.

Affected products

ProductAffected versionsFixed in
h3js h3 = >= 2.0.1-alpha.0, < 2.0.1-rc.17 No fix listed
npm h3(npm) >= 2.0.1-alpha.0, <= 2.0.1-rc.16 No fix listed
h3 = 2.0.1-rc1 No fix listed
h3 = 2.0.1-rc10 No fix listed
h3 = 2.0.1-rc11 No fix listed
h3 = 2.0.1-rc12 No fix listed
h3 = 2.0.1-rc13 No fix listed
h3 = 2.0.1-rc14 No fix listed
h3 = 2.0.1-rc15 No fix listed
h3 = 2.0.1-rc16 No fix listed
h3 = 2.0.1-rc2 No fix listed
h3 = 2.0.1-rc3 No fix listed
h3 = 2.0.1-rc4 No fix listed
h3 = 2.0.1-rc5 No fix listed
h3 = 2.0.1-rc6 No fix listed
h3 = 2.0.1-rc7 No fix listed
h3 = 2.0.1-rc8 No fix listed
h3 = 2.0.1-rc9 No fix listed
npm h3(npm) >= 2.0.1-alpha.0, < 2.0.1-rc.17 2.0.1-rc.17

References