[dependabot]

Bumps fast-uri from 3.1.8 to 3.1.9.

Release notes

Sourced from fast-uri's releases.

v3.1.9

Security

This security release fixes four URI parsing and normalization vulnerabilities in fast-uri 3.x. Applications that process untrusted URI input should upgrade to v3.1.9.

• Medium — URI scheme spoofing through percent-encoded schemes (GHSA-w74x-v6f9-j3xg, CVE-2026-110306): percent-encoded scheme input is now rejected instead of being decoded into a live scheme.
• Medium — Host confusion during domain-host canonicalization (GHSA-wjr9-j795-jxcr, CVE-2026-110180): malformed domain hosts containing ambiguous delimiters or stripped control characters are now rejected instead of being silently rewritten.
• Low — Incorrect relative-reference normalization (GHSA-xhq7-xmqj-769h, CVE-2026-110095): dot-segment removal now preserves the resolution semantics of relative references.
• Low — Scheme injection in suffix references (GHSA-333x-w4r6-6crp, CVE-2026-110725): first-segment colons in path-only suffix references are now escaped so the output is not reparsed as a scheme.

Upgrade with:

npm install fast-uri@3.1.9

Thanks to @​zekth for reporting the scheme, host, and relative-reference issues, and to @​UlisesGascon for finding the suffix-reference issue and reviewing the remediations.

What's Changed

• ci: enable trusted publishing releases (v3.x) by @​mcollina in fastify/fast-uri#229

Full Changelog: fastify/fast-uri@v3.1.8...v3.1.9

Commits

• 0def703 Bumped v3.1.9
• a1d0da2 test: generate only relative path references
• 9eb8759 fix: preserve relative paths in suffix and relative resolution
• 54c30f7 docs: note suffix-reference authority ambiguity
• 39e6493 fix: escape a first-segment colon in suffix references
• 745183c test: cover first-segment colon in suffix references
• ddfc6a5 fix(SEC-03): reject non reg-name characters in domain hosts
• d86a8d2 fix: keep a colon-first segment behind "./" in relative normalization
• eb483b5 test: cover colon-first relative references in normalization
• b110a35 fix(SEC-02): preserve meaning of relative references during normalization
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for fast-uri since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[maxigimenez]

Security triage: Tier B — ready, but wants a human decision

What and why

package	from	to	severity	via
fast-uri	3.1.8	3.1.9	moderate	ajv (runtime)

Four advisories close in this range, affected 3.0.0 - 3.1.8:

• GHSA-w74x-v6f9-j3xg — URI scheme spoofing via percent-encoded scheme decoding, CVSS 6.1, CWE-172/180
• GHSA-wjr9-j795-jxcr — host confusion via unchecked WHATWG host canonicalization, CVSS 4.8, CWE-20/436
• GHSA-xhq7-xmqj-769h — improper path equivalence in relative reference normalization, CVSS 3.7, CWE-41
• GHSA-333x-w4r6-6crp — scheme injection via an unescaped first-segment colon in suffix references, CVSS 3.7, CWE-41/116

No Vanta finding for this one either — it came from npm audit in mcp-server, so there is no remediateByDate and no SLA clock.

Exposure

Runtime. fast-uri resolves under one parent, ajv, with dev: false. mcp-server publishes @currents/mcp, so it reaches a shipped artifact. ajv uses fast-uri to resolve $ref and $id in JSON Schema documents, which is where the scheme- and host-confusion advisories bite.

The fix

Mechanism: dependabot-pr. The diff is one lockfile stanza, patch-level within 3.1.x — no manifest edit, no new override.

Breaking-change check

fast-uri 3.1.9 is a security patch over 3.1.8. No breaking-change, removal or deprecation section in range.

Verification

Not run locally this run — this PR does not qualify for auto-merge regardless (see below), so the CI evidence stands on its own:

check	conclusion
Test (Node 20.x)	success
Test (Node 22.x)	success
Test (Node 24.x)	success

CI coverage

Triggers test.yml on pull_request → main, no paths filter, so the lockfile-only diff does run it. Does not trigger publish.yaml, release.yaml or promote.yaml (workflow_dispatch), linear-release.yaml or post-release.yaml (push/close on main), or sync-from-monorepo.yaml (scheduled).

Why this does not auto-merge

Runtime dependencies never auto-merge, transitive or not. fast-uri reaches the published @currents/mcp package through ajv, which puts it outside the development-scope set that may merge unattended.

What a human should still check

1. Whether any JSON Schema compiled by ajv here resolves a $ref from input that a caller controls. If every schema is authored in-repo, the scheme- and host-confusion advisories have no reachable path and this is routine hygiene.
2. This needs a release to reach installed clients — worth batching with chore(deps): bump ip-address from 10.7.2 to 10.7.5 in /mcp-server #244 and the next @currents/mcp publish.

Needs release

@currents/mcp — the fix reaches clients only once published.

---

Generated by Claude Code