CVE-2026-75975: fast-uri vulnerable to server-side request forgery via malformed IPv6 normalization

Published Aug 24, 2026
·
Updated

fast-uri is a URI parser for Node.js. Its custom parser for bracketed IPv6 literals does not validate the complete IPv6 grammar, so invalid trailing text in an authority can be silently discarded and a malformed attacker-controlled host is turned into a different valid IPv6 destination. For example, a bracketed literal with invalid trailing characters is normalized to the unspecified address, which a Node HTTP client then connects to a local service over loopback, and other malformed literals collapse to private-range addresses. No error is set on the parsed result, so an application checking the error field cannot detect the rewrite. An application that normalizes untrusted URLs before outbound requests, redirects, proxy routing, or address-policy enforcement can be redirected to a local or private IPv6 target, giving a server-side request forgery and address-policy bypass primitive. The affected versions are 2.3.1 up to but not including 2.4.5, 3.0.0 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue is fixed in 2.4.5, 3.1.6, and 4.1.3, which validate bracketed IP literals against the full grammar and mark malformed literals as authority errors. Users should upgrade to a patched version.

Affected Software

3 affected components
npm/fast-uri>2.3.1<2.4.5
npm/fast-uri>3.0.0<3.1.6
npm/fast-uri>4.0.0<4.1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade fast-uri to a version that resolves this vulnerability.

    Fixed in 2.4.5
  2. Upgrade

    Upgrade fast-uri to a version that resolves this vulnerability.

    Fixed in 3.1.6
  3. Upgrade

    Upgrade fast-uri to a version that resolves this vulnerability.

    Fixed in 4.1.3

Event History

Aug 24, 2026
CVE Published
via MITRE·09:58 AM
Data Sourced
via MITRE·09:58 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which fast-uri versions contain the vulnerability, and which versions fix it?

Affected releases are 2.3.1 through before 2.4.5, 3.0.0 through before 3.1.6, and 4.0.0 through before 4.1.3. The fixes are available in 2.4.5, 3.1.6, and 4.1.3.

2

What conditions make an application practically exploitable?

An attacker must be able to supply a URL that the application normalizes before making outbound requests, following redirects, routing through a proxy, or enforcing an address policy. The malformed bracketed IPv6 authority can then be rewritten to a loopback or private IPv6 destination.

3

Can an application detect this issue by checking the parser error field?

No. The vulnerable parser does not set an error when it silently rewrites malformed bracketed IPv6 literals, so checking the parsed result's error field does not detect the rewrite.

4

How can I determine whether my application is exposed?

Check whether your dependency tree includes an affected fast-uri version and whether untrusted URLs reach code that uses fast-uri normalization for outbound HTTP requests, redirects, proxy routing, or destination-policy enforcement. Applications without such attacker-controlled URL flows are not described as having the SSRF path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203