Read the docs

IP spoofing in @fastify/proxy-addr via ignored IPv6 zone identifier

Priority MEDIUM 45CWE-290Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-290.

Summary

@fastify/proxy-addr from 3.0.0 before 5.1.3 is affected. When trustProxy is set to a zoned IPv6 link-local address, the trust comparison ignores the zone identifier (CWE-697), so a host on another link of a multi-homed server with the same link-local address is trusted. Such an attacker directly on one of those other links can spoof X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Proto headers, so the client IP, host and protocol that Fastify reports are attacker-chosen, which defeats IP allowlists, rate limiting and audit logging. The default configuration and global, private or loopback trust entries are not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

@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.

Why it matters now

Fix Fixed @fastify/proxy-addr (@fastify/proxy-addr): 5.1.3

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
@fastify/proxy-addr@fastify/proxy-addr3.0.0 to before 5.1.35.1.3Patch availableCNA
  • @fastify/proxy-addr Vendor@fastify/proxy-addr Affected 3.0.0 to before 5.1.3 Fixed in 5.1.3 Patch available CNA

Remediation

Upgrade @fastify/proxy-addr to 5.1.3 or later, which fixes the issue. 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.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA @fastify/proxy-addr (@fastify/proxy-addr) Fixed in 5.1.3

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-121192

References

  • TI-2026-62313 @fastify/proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet CVSS 3.1CRITICAL 9.1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences