Description
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.
Published: 2026-07-18
Score: 10 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

@fastify/http-proxy's handling of the rewritePrefix option contains a flaw. When the prefix includes URL‑encoded characters, the proxy does not rewrite the request path as intended, forwarding the raw encoded segment to the upstream server. This flaw allows an attacker to craft requests that reach internal or administrative endpoints that the proxy was meant to hide. The flaw can lead to unauthorized disclosure of sensitive data or further exploitation of the upstream service. Based on the description, it is inferred that an attacker could potentially use the exposed endpoints to compromise the upstream service if it contains additional vulnerabilities.

Affected Systems

This affects Node.js applications that use the @fastify/http-proxy package versions up to and including 11.5.0. The vulnerability is present whenever rewritePrefix is configured to remove path segments that could be URL‑encoded. Applications employing older versions of this package and exposing the proxy should be investigated. No specific operating system or platform is required beyond a Node.js runtime using Fastify.

Risk and Exploitability

The CVSS score is 10, indicating critical severity. The EPSS score is below 1%, meaning the probability of exploitation in the wild is low, and the vulnerability is not currently listed in the CISA KEV catalog. Nonetheless, the flaw can be triggered with a crafted HTTP request to the proxy, so all deployments using affected versions should address it immediately. The attack merely requires network access to the proxy endpoint; no privileged credentials are necessary.

Generated by OpenCVE AI on July 30, 2026 at 23:10 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade @fastify/http-proxy to version 11.6.0 or later
  • Restrict inbound traffic to the proxy with firewall rules to limit access to trusted networks
  • Verify upstream services are secured and not exposed directly to the Internet

Generated by OpenCVE AI on July 30, 2026 at 23:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 28 Jul 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Fastify
Fastify fastify-http-proxy
Vendors & Products Fastify
Fastify fastify-http-proxy

Mon, 20 Jul 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sat, 18 Jul 2026 13:45:00 +0000

Type Values Removed Values Added
Description 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.
Title @fastify/http-proxy vulnerable to prefix escape via URL-encoded characters
Weaknesses CWE-20
References
Metrics cvssV3_1

{'score': 10, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N'}


Subscriptions

Fastify Fastify-http-proxy
cve-icon MITRE

Status: PUBLISHED

Assigner: openjs

Published:

Updated: 2026-07-20T15:14:49.004Z

Reserved: 2026-07-17T15:40:14.822Z

Link: CVE-2026-16117

cve-icon Vulnrichment

Updated: 2026-07-20T15:14:44.605Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T23:15:06Z

Weaknesses
  • CWE-20

    Improper Input Validation