VulnerabilityPublished 28 Sep 2026

CVE-2026-84394: fast-uri vulnerable to host confusion via an unclosed bracket in the URI authority

Affects fast-uriSource GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.4.6 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.4.6, 3.1.7, 4.1.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 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 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade fast-uri to 2.4.6; fast-uri to 3.1.7; fast-uri to 4.1.4.

Affected software

Product	Affected	Fixed in
npmfast-uri	Affected >=2.4.5 <2.4.6 =2.4.5	Fixed in 2.4.6
npmfast-uri	Affected >=3.1.6 <3.1.7 =3.1.6	Fixed in 3.1.7
npmfast-uri	Affected >=4.1.3 <4.1.4 =4.1.3	Fixed in 4.1.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade fast-uri to version 2.4.6, 3.1.7, or 4.1.4 or later, where parse() correctly rejects malformed hosts with unbalanced brackets. If upgrading immediately is not possible, implement a workaround to reject any URL whose host contains '[' or ']' that is not a well-formed IPv6 literal before making host-based decisions.

Description

The fast-uri library has a vulnerability where it accepts hosts with unbalanced or misplaced brackets in the URI authority without error. This can cause discrepancies between the host parsed by fast-uri and the host resolved by Node.js URL clients, potentially leading to security bypasses in host-based access controls. The issue is fixed in fast-uri versions 2.4.6, 3.1.7, and 4.1.4.

Impact

An attacker can craft URLs with unclosed brackets in the host portion that fast-uri accepts without error but that Node.js clients resolve differently. This can lead to host confusion, allowing bypass of security controls that rely on fast-uri's host parsing for decisions such as SSRF protection, redirect allowlisting, or proxy routing. The vulnerability does not impact clients that fail closed on credential-bearing URLs, such as Node's global fetch().

Summary

fast-uri versions prior to 2.4.6, 3.1.7, and 4.1.4 accept hosts containing unbalanced or misplaced authority brackets (e.g., a host starting with '[' but missing a closing ']'). Such hosts are neither validated as IP literals nor canonicalized as domain names, causing parse() to return the malformed host without error. Meanwhile, Node.js URL clients resolve the same string to a different host (e.g., 127.0.0.1). This mismatch can allow an attacker to bypass host-based security checks like SSRF denylists or redirect allowlists if the application relies on fast-uri's parse().host for decisions but uses Node.js clients for requests. The vulnerability is identified as CVE-2026-84394 and has a CVSS 3.1 score of 7.5 (high severity).

CWE-436Interpretation Conflict (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Request Splitting (opens in a new tab)
HTTP Response Smuggling (opens in a new tab)
HTTP Response Splitting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 09:43 UTC

WeaknessesCWE-436

Technical details

References

Community reviews

Related threats