CVE-2026-33131: h3js h3 · Authentication Bypass by Spoofing
Affects h3js h3Source CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 2.0.1-rc.15 soon.
Data as of 1 Nov 2026, 08:20 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.1-rc.15
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 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 31 Oct 2026.
What to do
Upgrade h3js h3 to 2.0.1-rc.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| h3jsh3 | Affected
| Fixed in
|
AI-suggested
To mitigate this vulnerability, organizations should immediately upgrade all affected h3 framework instances to version 2.0.1-rc.15 or later, where the Host header spoofing issue is patched. Developers should audit middleware code that accesses event.url, event.url.hostname, or event.url._url to ensure that URL components are not constructed from unsanitized user input. Implement strict validation and sanitization of the Host header before using it in URL construction or routing logic. Consider adding explicit checks in middleware to verify that the Host header matches expected values or use server-side configuration to enforce allowed hosts. Additionally, review the order of middleware and route handler execution to prevent route resolution before security checks. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) to detect and block suspicious Host header manipulations. Finally, monitor application logs for unusual Host header values or access patterns that may indicate exploitation attempts.
Description
H3 is a minimal H(TTP) framework. Versions 2.0.0-0 through 2.0.1-rc.14 contain a Host header spoofing vulnerability in the NodeRequestUrl (which extends FastURL) which allows middleware bypass. When event.url, event.url.hostname, or event.url._url is accessed, such as in a logging middleware, the _url getter constructs a URL from untrusted data, including the user-controlled Host header. Because H3's router resolves the route handler before middleware runs, an attacker can supply a crafted Host header (e.g., Host: localhost:3000/abchehe?) to make the middleware path check fail while the route handler still matches, effectively bypassing authentication or authorization middleware. This affects any application built on H3 (including Nitro/Nuxt) that accesses event.url properties in middleware guarding sensitive routes. The issue requires an immediate fix to prevent FastURL.href from being constructed with unsanitized, attacker-controlled input. Version 2.0.1-rc.15 contains a patch for this issue.