Intel

AIKIDO-2026-662928

fast-uri is vulnerable to Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF)CVE-2026-86472 Published Yesterday

48

Medium Risk

This Affects:

JSfast-uri
0.0.1 - 2.4.6
Fixed in 2.4.7
3.0.0 - 3.1.7
Fixed in 3.1.8
4.0.0 - 4.1.4
Fixed in 4.1.5
Are you affected? Scan for Free

TL;DR

fast-uri only lowercases a percent-decoded host's ASCII letters for schemes that also run full path normalization, and a nested %-escape can still leave the fold incomplete elsewhere. equal() and resolve() therefore treat an encoded host such as a percent-encoded letter in metadata.internal as different from the literal spelling, even though both resolve to the same DNS name. Code that uses equal() or resolve() to allow or block a specific host can be bypassed by percent-encoding a letter in that hostname. The fix folds decoded reg-name characters to lowercase for every scheme before comparison.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you use equal or resolve to compare a URI's host against a trusted or blocked hostname.

Background info

fast-uri is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 2.4.6, 3.0.0 - 3.1.7 and 4.0.0 - 4.1.4.

How to fix this

Upgrade the fast-uri library to the patch version.

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform