Came across something in pnpm-lock.yaml around line 1 that looked worth flagging.
fast-uri 3.1.0 contains CVE‑2026‑13676: it fails to correctly canonicalize Unicode (IDN) hostnames for HTTP URLs. The library leaves the host in its original Unicode form while downstream Node URL/fetch parsers normalize it, allowing an attacker to craft a URL that bypasses host‑based security checks (e.g., deny‑lists, loopback filters, redirect validation). This can lead to SSRF, open‑redirect, or proxy‑routing bypasses, so the vulnerability is rated HIGH.
Something like this might fix it:
```diff
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@
- fast-uri@3.1.0:
- version "3.1.0"
- resolution {
- integrity "sha512-..."
- }
+ fast-uri@3.1.3:
+ version "3.1.3"
+ resolution {
+ integrity "sha512-..." # updated integrity hash for 3.1.3
+ }
```
For reference: rule CVE-2026-13676. Rated high.
The suggested change is untested against this project, so please read it before applying it.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.
Came across something in
pnpm-lock.yamlaround line 1 that looked worth flagging.fast-uri 3.1.0 contains CVE‑2026‑13676: it fails to correctly canonicalize Unicode (IDN) hostnames for HTTP URLs. The library leaves the host in its original Unicode form while downstream Node URL/fetch parsers normalize it, allowing an attacker to craft a URL that bypasses host‑based security checks (e.g., deny‑lists, loopback filters, redirect validation). This can lead to SSRF, open‑redirect, or proxy‑routing bypasses, so the vulnerability is rated HIGH.
Something like this might fix it:
For reference: rule
CVE-2026-13676. Rated high.The suggested change is untested against this project, so please read it before applying it.
Found with automated scanning (RedGem) and reviewed before opening. If it is not useful, closing it is completely fine.