CVE-2026-16117 CRITICAL

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

Vendor @Fastify/Http-Proxy
Product @fastify/http-proxy
Weakness CWE-20 · Input validation
Published July 18, 2026
Last update July 20, 2026

CVSS base score

10.0/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

What the vulnerability does

01Description

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 replace against the decoded prefix. A request that encodes one or more characters of the configured prefix therefore matches the route but skips the rewrite, so the raw encoded path is forwarded to the upstream unchanged. The upstream then decodes the path and serves it, letting an attacker reach upstream paths that the proxy was configured to hide via rewritePrefix, including internal or administrative endpoints. Patches: upgrade to @fastify/http-proxy 11.6.0. Workarounds: none.

Key dates

02Disclosure timeline

July 18, 2026 CVE published
July 20, 2026 Record updated

Related vulnerabilities

04Related CVE