CVE-2026-121192: @fastify/proxy-addr vulnerable to IP spoofing via ignored IPv6 zone identifier

Published Nov 16, 2026
·
Updated

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

Affected Software

1 affected component
npm/@fastify/proxy-addr>=3.0.0<=5.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade @fastify/proxy-addr to a version that resolves this vulnerability.

    Fixed in 5.1.3

Event History

Nov 16, 2026
CVE Published
via MITRE·12:55 PM
Data Sourced
via MITRE·12:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Exposure requires a multi-homed server with trustProxy configured to trust a zoned IPv6 link-local address. An attacker must be directly reachable on another link where the same link-local address exists; default configurations and global, private, or loopback trust entries are not affected.

2

What can an attacker control if exploitation succeeds?

An attacker can spoof X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Proto. This can cause Fastify to report attacker-chosen client IP, host, and protocol values, potentially bypassing IP allowlists or rate limits and corrupting audit logs.

3

How can this be remediated or mitigated?

Upgrade @fastify/proxy-addr to version 5.1.3 or later. If an upgrade cannot happen immediately, do not trust zoned link-local addresses on multi-homed hosts; configure trustProxy to use a global, private, or loopback proxy address instead.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203