chore(deps): update dependency fast-uri to v4.1.2 [security] - #2384
Merged
Conversation
Contributor
|
renovate
Bot
force-pushed
the
renovate/npm-fast-uri-vulnerability
branch
from
August 5, 2026 15:35
c19098b to
bef14bc
Compare
Contributor
|
paulushcgcj
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.1.1→4.1.2fast-uri vulnerable to host confusion via failed IDN canonicalization
CVE-2026-13676 / GHSA-4c8g-83qw-93j6
More information
Details
Impact
fast-uriversions>= 2.3.1, <= 4.0.0fail to canonicalize Unicode/IDN hostnames for HTTP-family URLs. The IDN conversion path callsURL.domainToASCII(...)on the global WHATWGURLconstructor, where that helper does not exist. The resultingTypeErroris silently routed intoparsed.error, butparse(),normalize(), andequal()all return with the host left in its original Unicode form.For example,
http://127。0。0。1/is treated byfast-urias host127。0。0。1, while Node's WHATWG URL parser andfetch()canonicalize the same input to127.0.0.1.Applications that use
fast-urito enforce host-based policy (denylists, loopback filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL orfetch()consumers see a policy/use desync and can be steered to an unintended destination.Patches
Upgrade to
fast-uriv4.0.1, v3.1.3, or v2.4.2Workarounds
None. Upgrade to the patched version.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
fast-uri vulnerable to host confusion via literal backslash authority delimiter
CVE-2026-16221 / GHSA-v2hh-gcrm-f6hx
More information
Details
Impact
fast-uriv4.1.0 and earlier do not treat a literal backslash (U+005C) as an authority delimiter. Node's native WHATWGURL(used byfetch(),undici, and Node'shttp/httpsclients) 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.comis treated byfast-urias hostallowed.comwith userinfoevil.com\, while Node's WHATWG URL parser andfetch()see hostevil.comwith path/@allowed.com.Applications that use
fast-urito enforce host-based policy (allowlists, denylists, loopback/SSRF filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL orfetch()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-uriv4.1.1, v3.1.4, or v2.4.3.Workarounds
None. Upgrade to the patched version.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
fast-uri vulnerable to host confusion via backslash authority introducer
CVE-2026-18446 / GHSA-7p8r-x3mc-p8w7
More information
Details
Impact
fast-uriv4.1.1 and earlier require a literal//to recognize a URI authority, so a reference that uses\\,/\, or\/as the authority introducer (in place of//, after an optional scheme) is parsed with no authority: the sequence and everything after it fold into the path. Node's native WHATWGURL(used byfetch(),undici, and Node'shttp/httpsclients) instead treats\as interchangeable with/for special schemes (http,https,ws,wss,ftp,file), so the two parsers extract different hosts from the same input.For example,
fast-uriresolves\\evil.com/pathagainst basehttps://allowed.com/tohttps://allowed.com/%5C%5Cevil.com/path(confined to the trusted host), while Node's WHATWG URL resolves the same reference tohttps://evil.com/path.Applications that use
fast-urito enforce host-based policy (allowlists, denylists, loopback/SSRF filtering, redirect validation, outbound proxy routing) before passing the same URL into Node's URL orfetch()consumers see a policy/use desync and can be steered to an unintended destination.Patches
Upgrade to
fast-uriv4.1.2, v3.1.5, v2.4.4.Workarounds
None. Upgrade to the patched version.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
fastify/fast-uri (fast-uri)
v4.1.2Compare Source
Fix for GHSA-7p8r-x3mc-p8w7
What's Changed
Full Changelog: fastify/fast-uri@v4.1.1...v4.1.2
Configuration
📅 Schedule: (in timezone America/Vancouver)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Thanks for the PR!
Deployments, as required, will be available below:
Any successful deployments (not always required) will be available here
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: