@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.
Severity
CVSS 3.1
6.8 medium
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-290Authentication Bypass by Spoofing CWE-697Incorrect Comparison
Show the promptExplain CVE-2026-121192 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121192?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121192?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121192 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.