Description
Leading control characters in a URL are not stripped when passed into url-parse. This can cause input URLs to be mistakenly be interpreted as a relative URL without a hostname and protocol, while the WHATWG URL parser will trim control characters and treat it as an absolute URL.
Recommendation
Update the url-parse package to the latest compatible version. Followings are version details:
- Affected version(s): >= 0.1.0, < 1.5.9
- Patched version(s): 1.5.9
References
Could your website be exposed too?
SmartScanner can check your website for url-parse incorrectly parses hostname / protocol due to unstripped leading control characters. and gives you actionable findings to investigate.
Start a free scanRelated Issues
- url-parse Incorrectly parses URLs that include an '@ - CVE-2022-0639
- parse-url parses http URLs incorrectly, making it vulnerable to host name spoofing - CVE-2022-3224
- Hostname confusion in parse-url - CVE-2022-0722
- Authorization bypass in url-parse - CVE-2022-0512
You might also like:
See something that needs correcting? Let us knowUpdated February 03, 2026