@cedarjs/api-server (>=1.0.0-canary.12281, <=9.0.0-canary.1784), @cedarjs/cli (>=1.0.0-canary.12281, <=9.0.0-canary.1784) +40 more potentially affected by CVE-2026-16117 via @fastify/http-proxy (>=11.1.2, <=11.5.0)

@fastify/http-proxy NPM version =11.1.2, =1.0.0-canary.12281, =1.0.0-canary.12281, =6.0.0-canary.2685, =1.0.0-canary.12281, =1.0.0-canary.12281, =4.0.0-canary.13864, =4.0.0-canary.13864, =1.0.0-canary.12281, =3.0.0-alpha-1, =0.0.4, =0.3.0, =0.1.0, =1.0.1, =1.0.14 and more Source cves:...

CVE-2026-16117

creationtimestamp| type| source ---|---|--- 2026-07-18 13:14:19+00:00| seen| https://bsky.app/profile/ulisesgascon.com/post/3mqwdtonr6k25 2026-07-18 14:36:06+00:00| seen| https://bsky.app/profile/stackflag.bsky.social/post/3mqwifxu7mz2z 2026-07-18 15:00:46+00:00| seen|...

CVE-2026-16117

The CVE concerns @fastify/http-proxy (affected: up to 11.5.0) where URL prefix rewriting fails when the prefix segment is URL-encoded. Fastify decodes paths for route matching, but request.url keeps the original encoded form. The prefixRewrite step compares against the decoded prefix using a lite...

CVE-2026-16117 @fastify/http-proxy vulnerable to prefix escape via URL-encoded characters

Impact: @fastify/http-proxy versions up to and including 11.5.0 fail to rewrite the request prefix when the prefix segment is URL-encoded. Fastify's router URL-decodes paths for route matching, but request.url retains the original encoded form, and the prefix-rewrite step uses a literal string...