Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft URL with literal backslash in authority
-
DeliverySubmit to app's host-policy check
-
Exploitfast-uri approves benign-looking host
-
ExecutionNode parser normalizes backslash, resolves internal host
-
PersistOutbound request hits metadata/loopback endpoint
-
ImpactExfiltrate credentials or internal data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V4 - API and Web Service Interpretation consistency
|
| Exploitation Conditions | Exploitation requires that the target application (1) uses fast-uri at an affected version (2.3.1-4.1.0) to parse or extract the host from an attacker-influenced URL, (2) makes a security decision on that host - allowlist, denylist, loopback/SSRF filter, redirect validation, or outbound proxy routing - and (3) then passes the SAME raw URL string into a Node consumer backed by the WHATWG URL parser (fetch, undici, http, or https clients) for the actual request. The scheme must be a WHATWG 'special' scheme (http, https, ws, wss, ftp, or file) for Node's backslash-to-slash normalization to trigger. What limits exploitation: the two-parser split-decision pattern must exist in the application - deployments that use fast-uri only for schema validation, or that use the same parser for both the check and the request, are not exploitable. No authentication (PR:N) or user interaction (UI:N) is required where the vulnerable pattern is present. |
| Impact | The published CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yields 7.5 (High), modeling an unauthenticated network attacker who bypasses integrity-relevant host controls. In practice the real risk is conditional: the vulnerability only matters when an application uses fast-uri to enforce host-based policy and then hands the same raw URL to a Node fetch/undici/http consumer - this is a specific integration pattern, so the effective attack complexity is higher than AC:L suggests for arbitrary deployments. There is no EPSS score, no CISA KEV listing, and no POC in the provided intelligence, so this is not confirmed as actively exploited; it should be treated as a latent SSRF-enabler rather than a mass-exploited flaw. The impact where the pattern exists is serious (SSRF to cloud metadata can yield credential theft), so the C:N in the vendor vector is arguably understated - SSRF typically carries confidentiality impact. Priority is high for any Node service performing URL allowlisting/SSRF filtering with fast-uri; low for deployments that only use it for schema validation. |
| Exploit ScenarioDerived | An attacker submits a URL such as http:\\attacker-controlled\@169.254.169.254/ (or similar backslash-laden authority) to a Node application that validates the host with fast-uri and then fetches it via undici/fetch. fast-uri parses one host and approves it against the allowlist while Node's parser normalizes the backslash and connects to a different host - the cloud metadata endpoint - returning IAM credentials to the attacker. No authentication or user interaction is required per the CVSS vector, and no public POC is currently identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 19, 2026
Host-based policy bypass in the fast-uri Node.js URI parser (versions 2.3.1 through 4.1.0, spanning the 2.x line up to 2.4.2 and the 3.x line up to 3.1.3) allows remote attackers to smuggle a different host past allowlist, denylist, SSRF, loopback, and redirect-validation checks by using a literal backslash. Because fast-uri does not treat U+005C as an authority delimiter while Node's native WHATWG URL parser (used by fetch, undici, and the http/https clients) normalizes backslash to forward slash for special schemes, the two parsers disagree on the host, enabling requests to be steered to cloud metadata, loopback, or internal endpoints. There is no public exploit identified at time of analysis, but the flaw is trivially triggerable in affected deployments and openjsf has published a fix.
RemediationAI
Vendor-released patch: upgrade fast-uri to 4.1.1 (4.x line), 3.1.4 (3.x line), or 2.4.3 (2.x line) depending on the major version you run; these releases make fast-uri treat a literal backslash consistently so its host extraction aligns with Node's WHATWG parser. The vendor states there are no workarounds, so patching is the required fix. As interim compensating controls until you can upgrade, reject or normalize any URL whose authority or path contains a backslash before it reaches your policy check (fail closed on U+005C), and standardize on a single parser end-to-end - use Node's native URL/WHATWG parser for BOTH the security decision and the outbound request so the two cannot disagree; the trade-off is that pre-normalizing input may break rare legitimate URLs containing encoded backslashes. Where feasible, enforce SSRF protection at the network layer as defense in depth by blocking outbound access to 169.254.169.254 and other metadata/loopback/internal ranges from application egress. Track fixes via GHSA-v2hh-gcrm-f6hx (https://github.com/fastify/fast-uri/security/advisories/GHSA-v2hh-gcrm-f6hx).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is fast-uri, a high-performance RFC 3986 URI parser widely used in the Fastify ecosystem (notably as ajv's URI resolver) as a drop-in replacement for uri-js. The root cause is classified as CWE-436 (Interpretation Conflict / parser differential): fast-uri follows strict RFC 3986 semantics where a backslash is a normal path character and not part of the authority, whereas Node's built-in WHATWG URL parser - the one backing fetch, undici, and the native http/https clients - applies WHATWG special-scheme normalization that rewrites backslashes to forward slashes for http, https, ws, wss, ftp, and file URLs. When one library extracts the host for a security decision and a different library extracts the host for the actual outbound request, the same input string resolves to two different destinations. The single affected CPE is cpe:2.3:a:fast-uri:fast-uri:*:*:*:*:*:*:*:*.
Know when Fast Uri gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
AC:H because exploitation needs the specific fast-uri-check-then-Node-fetch pattern; PR:N/UI:N as attacker-supplied URLs suffice; C:H reflects SSRF to metadata/internal resources over I:N.
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Primary rating from Vendor (openjs).
CVSS VectorVendor: openjs
Lifecycle Timeline
2DescriptionCVE.org
Impact: fast-uri versions from 2.3.1 through 4.1.0 (including the 3.x line up to 3.1.3 and the 2.x line up to 2.4.2) do not treat a literal backslash character (U+005C) as an authority delimiter. Node's native WHATWG URL parser, used by fetch, undici, and Node's http and https clients, normalizes the backslash to a forward slash for special schemes such as http, https, ws, wss, ftp, and file. As a result, the two parsers extract different hosts from the same input string. Applications that use fast-uri to enforce host-based policy such as allowlists, denylists, loopback or SSRF filtering, redirect validation, or outbound proxy routing before passing the same URL into Node's URL or fetch consumers can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts.
Patches: upgrade to fast-uri 4.1.1, 3.1.4, or 2.4.3.
Workarounds: none.
Executive ViewAI
The fast-uri Node.js library used for URL security validation in web applications contains a host-validation bypass that allows attackers to circumvent access controls and reach cloud metadata services and internal resources. The vulnerability is straightforward to exploit, and organizations using affected versions (2.3.1-2.4.2 or 3.0.0-3.1.3) risk unauthorized exposure of cloud credentials and internal infrastructure. Urgent patching is required to prevent compromise.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Host confusion in fast-uri, a Node.js URI parser in the Fastify ecosystem, allows policy bypass by exploiting inconsiste
Server-side request forgery and address-policy bypass in fast-uri, the Node.js URI parser used widely in the fastify eco
Double-decoding of percent-encoded hostnames in fast-uri (Node.js URI parser) creates a server-side request forgery and
Host-based security policy bypass in the fast-uri Node.js URI parser (versions 2.3.1 through 3.1.2 and 4.0.0) lets remot
Parsing and serialization inconsistency in fast-uri, the Node.js URI parser core to the Fastify ecosystem, allows networ
URI authority injection in fast-uri allows an attacker-supplied port value containing delimiter characters to demote the
Security filter bypass in fast-uri (before versions 4.1.2, 3.1.5, and 2.4.4) enables unauthenticated remote attackers to
Path normalization bypass in fast-uri 3.1.0 and earlier allows remote attackers to circumvent path-based access controls
Authority confusion in fast-uri JavaScript library allows remote attackers to bypass URL validation security controls. T
Host-parsing ambiguity in fast-uri allows attackers to silently bypass SSRF denylists, redirect allowlists, and proxy ro
The mailto scheme parser added to fast-uri 4.1.3 (and still present in 4.1.4) compares query field names against the res
Host allowlist and denylist bypass in fast-uri, the dependency-free RFC 3986 URI parser used by Fastify and ajv, affects
Same weakness CWE-436 – Interpretation Conflict
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Linux Enterprise Micro 5.3 | Not-Affected |
| SUSE Linux Enterprise Micro 5.3 | Not-Affected |
| SUSE Linux Enterprise Micro 5.3 | Not-Affected |
| SUSE Linux Enterprise Micro 5.3 | Not-Affected |
| SUSE Linux Enterprise Micro 5.4 | Not-Affected |
| SUSE Linux Enterprise Micro 5.4 | Not-Affected |
| SUSE Linux Enterprise Micro 5.4 | Not-Affected |
| SUSE Linux Enterprise Micro 5.4 | Not-Affected |
| SUSE Linux Enterprise Micro 5.5 | Not-Affected |
| SUSE Linux Enterprise Micro 5.5 | Not-Affected |
| SUSE Linux Enterprise Micro 5.5 | Not-Affected |
| SUSE Linux Enterprise Micro 5.5 | Not-Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server 16.0 | Affected |
| SUSE Linux Enterprise Server 16.0 | Affected |
| SUSE Linux Enterprise Server 16.0 | Affected |
| SUSE Linux Enterprise Server 16.0 | Affected |
| SUSE Linux Enterprise Server 16.0 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Micro 6.0 | Not-Affected |
| SUSE Linux Micro 6.0 | Not-Affected |
| SUSE Linux Micro 6.0 | Affected |
| SUSE Linux Micro 6.0 | Not-Affected |
| SUSE Linux Micro 6.1 | Affected |
| SUSE Linux Micro 6.1 | Not-Affected |
| SUSE Linux Micro 6.1 | Not-Affected |
| SUSE Linux Micro 6.1 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| SUSE Linux Micro 6.2 | Affected |
| openSUSE Leap 16.0 | Affected |
| openSUSE Leap 16.0 | Affected |
| openSUSE Leap 16.0 | Affected |
| openSUSE Leap 16.0 | Affected |
| openSUSE Leap 16.0 | Affected |
| openSUSE Leap 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP3 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP4 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP5 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP3 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP4 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | Affected |
| openSUSE Leap Micro 5.5 | Not-Affected |
| openSUSE Leap Micro 5.5 | Not-Affected |
| openSUSE Leap Micro 5.5 | Not-Affected |
EUVD-2026-45551
GHSA-v2hh-gcrm-f6hx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB