CVE-2026-121192 json
@fastify/proxy-addr vulnerable to IP spoofing via ignored IPv6 zone identifier
published yesterday modified 10h ago also EUVD-2026-126370 , GHSA-fmr2-3fr5-78g8
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository fastify/proxy-addr. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
@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.
Patch / fix
- npm @fastify/proxy-addr 5.1.3
- @fastify/proxy-addr @fastify/proxy-addr 5.1.3
Is CVE-2026-121192 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11h ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-17).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @fastify/proxy-addr | >=3.0.0, <5.1.3 |
5.1.3 |
Affected products
- @fastify/proxy-addr @fastify/proxy-addr
Classification
References
Sources
- CVE List CVE-2026-121192
- NVD CVE-2026-121192
- Maintainer advisory GHSA-fmr2-3fr5-78g8
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of fastify/proxy-addr published their own advisory on GitHub. Reviewed sources take precedence over it.