Quick answers
- Is CVE-2026-84292 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84292 being exploited in the wild.
- How severe is CVE-2026-84292?
- High severity, with a CVSS score of 7.5, published 2 September 2026.
- Which products and versions are affected?
- fast-uri (npm) SEMVER:introduced=0,fixed=2.4.6.
- Is there a fix for CVE-2026-84292?
- Yes. fast-uri (npm): upgrade to 2.4.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84292 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84292?
- Check whether you run fast-uri (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- fast-uri (npm): upgrade to 2.4.6 or later
npm install fast-uri@2.4.6
Technical details
The vulnerability is an improper encoding/escaping issue (CWE-116) in fast-uri's recomposeAuthority function. When serializing a URI, the library properly escapes userinfo and host components but concatenates the port value verbatim without validating that it contains only digits per RFC 3986. An attacker can inject authority delimiters (such as @) in the port parameter, which reorders the URI structure—demoting the intended host to the userinfo section and inserting an attacker-controlled host as the actual authority. The attack is network-reachable with no authentication or user interaction required and affects applications that construct URIs from untrusted port values via serialize(), normalize(), or equal() methods. Patches are available in fast-uri 2.4.6, 3.1.7, and 4.1.4, which now validate that the port is a digit sequence.
Affected products
- OpenJS Foundation fast-uri before 2.4.6, 3.0.0 before 3.1.7, 4.0.0 before 4.1.4
Identifiers
- CVE-2026-84292
- GHSA-qw65-cvwx-89v3
Timeline
- 2026-09-02: disclosed: CVE-2026-84292 published
- 2026-09-02: patched: Patches released in versions 2.4.6, 3.1.7, and 4.1.4