CVE-2026-121192
Medium 6.8No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 25% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-290, CWE-697
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.