CVE-2026-33732 | h3js srvx up to 0.11.12 HTTP Request name resolution
VulDBArchived Mar 26, 2026✓ Full text saved
A vulnerability was found in h3js srvx up to 0.11.12 and classified as problematic . Affected by this vulnerability is an unknown functionality of the component HTTP Request Handler . Such manipulation leads to incorrectly-resolved name. This vulnerability is uniquely identified as CVE-2026-33732 . The attack can be launched remotely. No exploit exists. It is suggested to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353673 · CVE-2026-33732 · GCVE-0-2026-33732
H3JS SRVX UP TO 0.11.12 HTTP REQUEST NAME RESOLUTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.1 $0-$5k 1.81+
Summaryinfo
A vulnerability was found in h3js srvx up to 0.11.12. It has been classified as problematic. Affected by this issue is some unknown functionality of the component HTTP Request Handler. Performing a manipulation results in name resolution. This vulnerability was named CVE-2026-33732. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.
Detailsinfo
A vulnerability classified as problematic has been found in h3js srvx up to 0.11.12. This affects an unknown code block of the component HTTP Request Handler. The manipulation with an unknown input leads to a name resolution vulnerability. CWE is classifying the issue as CWE-706. The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
srvx is a universal server based on web standards. Prior to version 0.11.13, a pathname parsing discrepancy in srvx's `FastURL` allows middleware bypass on the Node.js adapter when a raw HTTP request uses an absolute URI with a non-standard scheme (e.g. `file://`). Starting in version 0.11.13, the `FastURL` constructor now deopts to native `URL` for any string not starting with `/`, ensuring consistent pathname resolution.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-33732 since 03/23/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.11.13 eliminates this vulnerability.
Productinfo
Vendor
h3js
Name
srvx
Version
0.11.0
0.11.1
0.11.2
0.11.3
0.11.4
0.11.5
0.11.6
0.11.7
0.11.8
0.11.9
0.11.10
0.11.11
0.11.12
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.2
VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.8
CNA Vector (GitHub_M): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Name resolution
CWE: CWE-706
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: srvx 0.11.13
Timelineinfo
03/23/2026 CVE reserved
03/26/2026 +3 days Advisory disclosed
03/26/2026 +0 days VulDB entry created
03/26/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-33732 (🔒)
GCVE (CVE): GCVE-0-2026-33732
GCVE (VulDB): GCVE-100-353673
Entryinfo
Created: 03/26/2026 18:59
Changes: 03/26/2026 18:59 (63)
Complete: 🔍
Cache ID: 99:1F4:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸