Possible fix(deps): 3 vulnerable dependencies in package-lock.json

[begininvoke]

Came across something in package-lock.json around line 4069 that looked worth flagging.

The vulnerability is real: fast-uri versions 2.3.1‑3.1.2 (and 4.0.0) fail to properly canonicalize Unicode IDN hostnames. The library’s IDN handling calls a helper that does not exist in the global URL constructor, leaving the host in its original Unicode form. This causes a mismatch between fast-uri’s normalize()/equal() results and what a WHATWG‑compatible parser (e.g., Node’s URL or fetch) would produce. Consequently, applications that enforce host‑based policies (denylists, loopback filters, redirect validation, outbound proxy routing) using fast-uri can be bypassed when the same URL later resolves to a different host after being processed by Node’s native parser. The fix is to upgrade fast-uri to a patched version (3.1.3 for the 3.x line, or 4.0.1 for the 4.x line).

Something like this might fix it:

--- a/package.json
+++ b/package.json
@@ -8,7 +8,7 @@
   "dependencies": {
-    "fast-uri": "3.1.2",
+    "fast-uri": "3.1.3",
    "other-package": "^1.2.3"
   }

For reference: rule CVE-2026-13676. Rated high.

I do not maintain this project, so I may well be missing context — if this is intentional or already handled elsewhere, please just close it.

---

Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.

[Waishnav]

Thanks for flagging this. The vulnerable fast-uri version is present transitively through the MCP SDK -> Ajv dependency chain, but this does not look like a major DevSpace exploit concern right now: DevSpace does not use fast-uri directly for host allowlisting or outbound URL policy, and the security-sensitive URL checks I traced use Node’s WHATWG URL parser before comparing hosts. So I do not see the parser-confusion pattern required for the reported bypass in our current code path.\n\nWe should still clean it up because shipping a known-vulnerable transitive dependency is unnecessary. One correction to the suggested fix: 3.1.3 is no longer sufficient due to later fast-uri advisories, so I’m going to update the resolved 3.x version to the current patched release instead.