What’s Vulnerable › Vulnerabilities
CVE-2026-33490: h3: Missing Path Segment Boundary Check in `mount()` Causes Middleware Execution on Unrelated Prefix-Matching Routes
- Severity: medium (CVSS 5.3 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2026-03-26 · updated 2026-06-17
- Weakness: CWE-706
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
- h3js h3: 2.0.1-rc1, 2.0.1-rc10, 2.0.1-rc11, 2.0.1-rc12, 2.0.1-rc13, 2.0.1-rc14 (+10)
References
- https://github.com/h3js/h3/security/advisories/GHSA-2j6q-whv2-gh6w
- https://github.com/h3js/h3/security/advisories/GHSA-2j6q-whv2-gh6w
Get alerted when CVE-2026-33490 or the next vulnerability affects your stack