CVE-2026-121192 · Package
NO FIX YET · SEE WHAT TO DO
@fastify/proxy-addr ignores the zone identifier when checking a zoned IPv6 link-local trustProxy address, so a host on another link with the same address is trusted. That lets an attacker spoof X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Proto, defeating IP allowlists, rate limiting and audit logs.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only applications using Fastify with trustProxy set to a zoned IPv6 link-local address on a multi-homed server are exposed. An attacker must be directly on one of the other links of that server. Default configurations and global, private or loopback trust entries are not affected; a workaround is to trust a global, private or loopback proxy address instead.
Not affected if default-config, global-or-loopback-trustproxy, single-homed-host
Who cares fastify, node, self-hosted
npm ls @fastify/proxy-addr (versions 3.0.0 through 5.1.2 are affected).trustProxy in the Fastify configuration is set to a zoned IPv6 link-local address (one containing a % zone such as fe80::1%eth1).@fastify/proxy-addr 5.1.3 or later@fastify/proxy-addr determines which network hops are trusted proxies and backs Fastify's trustProxy setting, so that forwarded headers can be believed. In versions 3.0.0 through 5.1.2, when trustProxy is configured with a zoned IPv6 link-local address, the trust comparison checks only the address bits and ignores the zone identifier, so a host on another link of a multi-homed server that carries the same link-local address is trusted as well. Such an attacker can spoof the X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Proto headers, making the client IP, host and protocol reported by Fastify attacker-chosen values and defeating IP allowlists, rate limiting and audit logging. Exploitation requires a multi-homed server whose trustProxy is a zoned link-local address and an attacker directly on one of its other links; the default configuration and global, private or loopback trust entries are not affected. The issue is fixed in @fastify/proxy-addr 5.1.3, and users should upgrade to 5.1.3 or later. As a workaround, avoid trusting a zoned link-local address on a multi-homed host and trust a global, private or loopback proxy address instead.
This page as .md ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.