NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

fast-uri vulnerable to host confusion via literal backslash authority delimiterGHSA-v2hh-gcrm-f6hx

HIGHFix: fastify/fast-uri@0542a21

GHSA-v2hh-gcrm-f6hx is a high-severity (CVSS 7.5) CWE-436 vulnerability in fast-uri. A fix is available for fast-uri — see the affected versions and patch details below.

Also known asCVE-2026-16221
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v2hh-gcrm-f6hx.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk
0.00%0.31%0.62%0.94%0.2%0.4%0.3%0.4%0.4%Aug 26Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

361other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
fast-urinpm
233.5Mdownloads / week

Description

Impact

fast-uri v4.1.0 and earlier do not treat a literal backslash (U+005C) as an authority delimiter. Node's native WHATWG URL (used by fetch(), undici, and Node's http/https clients) normalizes \ to / for special schemes (http, https, ws, wss, ftp, file), so the two parsers extract different hosts from the same input string.

For example, http://evil.com\@allowed.com is treated by fast-uri as host allowed.com with userinfo evil.com\, while Node's WHATWG URL parser and fetch() see host evil.com with path /@allowed.com.

Applications that use fast-uri to enforce host-based policy (allowlists, denylists, loopback/SSRF filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL or fetch() consumers see a policy/use desync and can be steered to an unintended destination, including cloud metadata endpoints, loopback, or internal hosts.

Patches

Upgrade to fast-uri v4.1.1, v3.1.4, or v2.4.3.

Workarounds

None. Upgrade to the patched version.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npmfast-uri≥ 2.3.1&&< 2.4.32.4.3npm install fast-uri@2.4.3
📦npmfast-uri≥ 3.0.0&&< 3.1.43.1.4npm install fast-uri@3.1.4
📦npmfast-uri≥ 4.0.0&&< 4.1.14.1.1npm install fast-uri@4.1.1

Affected Products

1 product · 3 configurations
Application
fast-uriopenjsf
≥ 4.0.0 && < 4.1.1
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-uri, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update fast-uri to 2.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2hh-gcrm-f6hx is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Important: This flaw in fast-uri allows for a security policy bypass due to inconsistent URL parsing between fast-uri and Node.js's native WHATWG URL parser. Applications within Red Hat Hardened Images that rely on fast-uri for host-based policy enforcement, such as allowlists or Server-Side Request Forgery (SSRF)…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for GHSA-v2hh-gcrm-f6hx (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Hardened Imagesgrafana13-1-main-13.1.3-0.1.1.hum1RHSA-2026:54517
Red Hat Hardened Imagesgrafana12-4-main-12.4.8-0.1.1.hum1RHSA-2026:54518
Red Hat Migration Toolkit 1.8rhmtc/openshift-migration-ui-rhel8:1789546373RHSA-2026:68681
Red Hat OpenShift AI 2.25rhoai/odh-mod-arch-model-registry-rhel9:1791853432RHSA-2026:87410
Red Hat OpenShift AI 3.3rhoai/odh-mod-arch-gen-ai-rhel9:1790128173RHSA-2026:73987
Red Hat OpenShift AI 3.4rhoai/odh-dashboard-rhel9:1791861020RHSA-2026:84734
Red Hat OpenShift AI 3.4rhoai/odh-mod-arch-gen-ai-rhel9:1793001896RHSA-2026:92510
Red Hat OpenShift Container Platform 4.21openshift4/nmstate-console-plugin-rhel9:1789592806RHSA-2026:68547

Frequently Asked Questions

### Impact `fast-uri` v4.1.0 and earlier do not treat a literal backslash (U+005C) as an authority delimiter. Node's native WHATWG `URL` (used by `fetch()`, `undici`, and Node's `http`/`https` clients) normalizes `\` to `/` for special schemes (`http`, `https`, `ws`, `wss`, `ftp`, `file`), so the two parsers extract different hosts from the same input string. For example, `http://evil.com\@allowed.com` is treated by `fast-uri` as host `allowed.com` with userinfo `evil.com\`, while Node's WHATWG URL parser and `fetch()` see host `evil.com` with path `/@allowed.com`. Applications that use `fa
O3 Security · Impact-Aware SCA

Is GHSA-v2hh-gcrm-f6hx in your dependencies?

Find it across npm, including transitive dependencies.

GHSA-v2hh-gcrm-f6hx: fast-uri SSRF — Fixed in 2.4.3