Skip to content

fast-uri vulnerable to URI scheme spoofing via percent-encoded scheme decoding

Moderate severity GitHub Reviewed Published Oct 19, 2026 in fastify/fast-uri • Updated Oct 23, 2026

Package

npm fast-uri (npm)

Affected versions

< 2.4.8
>= 3.0.0, < 3.1.9
>= 4.0.0, < 4.2.3

Patched versions

2.4.8
3.1.9
4.2.3

Description

Impact

fast-uri percent-decodes the scheme component with the legacy global unescape() before validating it, so an input whose decoded scheme is a valid but dangerous token is emitted as a live scheme. RFC 3986 section 3.1 does not allow percent-encoding in a scheme, so no RFC or WHATWG parser treats such input as having that scheme, but fast-uri does.

For example, normalize('%6Aavascript:alert(1)') returns javascript:alert(1), resolve('https://a.example/', '%6Aavascript:alert(1)') returns javascript:alert(1), and parse('%6Aavascript:alert(1)').scheme returns javascript. The %uXXXX form (%u006Aavascript:) produces the same result, and equal('%68ttp://a/', 'http://a/') returns true.

An application that screens dangerous schemes on the raw input and then stores or renders normalize(input) or resolve(base, input) turns an inert string into an executable javascript:, data:, or vbscript: URL, a stored or reflected cross-site scripting vector in the consuming application. equal() also treats an encoded and a plain scheme as the same, which can bypass equality-based allowlists.

Patches

Upgrade to fast-uri 2.4.8, 3.1.9, or 4.2.3.

Workarounds

Reject input whose scheme part (before the first :, and before any /, ?, or #) contains %. Alternatively, check parse(x).scheme against an allowlist after normalization and use that same parsed result rather than the raw string.

References

@mcollina mcollina published to fastify/fast-uri Oct 19, 2026
Published by the National Vulnerability Database Oct 20, 2026
Published to the GitHub Advisory Database Oct 23, 2026
Reviewed Oct 23, 2026
Last updated Oct 23, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(16th percentile)

Weaknesses

Improper Encoding or Decoding of Data

The product does not properly encode or decode data, resulting in unexpected values that are not equivalent to the original data. Learn more on MITRE.

Incorrect Behavior Order: Validate Before Canonicalize

The product validates input before it is canonicalized. Learn more on MITRE.

CVE ID

CVE-2026-110306

GHSA ID

GHSA-w74x-v6f9-j3xg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.