This behavior is dangerous for applications using fast-uri to parse URLs for security decisions, such as SSRF denylists, redirect allowlists, or proxy routing. Because the library incorrectly identifies the host, a security policy may be evaluated against a malformed string while the final network request, performed by downstream libraries like axios, got, or Node.js's http.get, resolves the URI differently. This allows an attacker to route requests to restricted internal IP addresses or domains that the application intended to block.

Impact

Successful exploitation allows for the bypass of security controls relying on fast-uri for URL validation. This can lead to Server-Side Request Forgery (SSRF) in applications that perform outgoing HTTP requests based on user-supplied URLs. Any web application or proxy service using these versions of fast-uri to make security decisions regarding URL reachability or internal resource access is at risk.

Recommendation

Prioritized, concrete actions for security teams:

• Upgrade fast-uri to versions 4.1.4, 3.1.7, or 2.4.6 immediately to implement strict validation of URI host brackets.
• If upgrading is not possible, implement a secondary validation layer in your application that rejects any URL where the host contains [ or ] characters unless the entire host string matches the formal definition of an IPv6 literal (i.e., enclosed in brackets and containing valid IPv6 syntax).
• Review application logic that uses fast-uri.parse().host to make authorization or routing decisions to ensure the parsed host matches the intended destination.
• Audit logs for instances where external URL parameters include unexpected bracket characters, which may indicate exploitation attempts.