Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 16 Nov 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @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. | |
| Title | @fastify/proxy-addr vulnerable to IP spoofing via ignored IPv6 zone identifier | |
| Weaknesses | CWE-290 CWE-697 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: openjs
Published:
Updated: 2026-11-16T12:55:59.956Z
Reserved: 2026-11-03T10:24:31.085Z
Link: CVE-2026-121192
No data.
Status : Awaiting Analysis
Published: 2026-11-16T13:17:20.860
Modified: 2026-11-16T20:37:04.673
Link: CVE-2026-121192
No data.
OpenCVE Enrichment
Updated: 2026-11-16T15:00:09Z