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

> Attackers on another link of a multi-homed server can spoof forwarded headers, defeating IP allowlists, rate limiting and audit logging in Fastify apps using zoned trustProxy.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-fmr2-3fr5-78g8, UBUNTU-CVE-2026-121192

## What is CVE-2026-121192?

CVE-2026-121192 is a medium-severity security feature bypass vulnerability in @fastify/proxy-addr, published on 16 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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-697 (Incorrect Comparison), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-121192?

1 open source package ship an affected version, including %40fastify/proxy-addr.

An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `%40fastify/proxy-addr` | npm | `pkg:npm/%40fastify/proxy-addr` | From 3.0.0 | 5.1.3 |

## How do I fix CVE-2026-121192?

Upgrade each affected package to the fixed version listed for it above. Each package has its own fixed versions.

## Is CVE-2026-121192 being exploited?

There is no known exploitation of CVE-2026-121192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121192 and fix it if it is affected.

What it is: CVE-2026-121192 is a medium-severity security feature bypass vulnerability in @fastify/proxy-addr, published on 16 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-121192 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.

Affected packages and fixed versions:
- %40fastify/proxy-addr (npm): affected from 3.0.0; fixed in 5.1.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121192/ (Markdown: https://insights.sbomify.com/CVE-2026-121192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121192
- OSV: https://osv.dev/vulnerability/CVE-2026-121192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121192/
Summaries are generated and may contain mistakes; the official description above is the record.
