Fastify Proxy Address Fix Preserves IPv6 Link-Local Trust Boundaries
Quick Answer
Update @fastify/proxy-addr to 5.1.3 or later. Review zoned link-local trustProxy entries and verify client-IP controls across each connected interface.
Confirm Scope And Apply The Supported Remediation
What to do now: Record resolved proxy-addr versions, trustProxy values, network interfaces and controls that rely on request.ip, request.ips, request.host or request.protocol. The default trustProxy: false and global, private or loopback proxy addresses are outside this specific flaw. Verify the configured zone and whether untrusted hosts can reach another local link. Install 5.1.3 or later and redeploy the resolved dependency. If deployment must wait, use a suitable global, private or loopback proxy address, or restrict reachability to the intended proxy link. Test accepted and rejected forwarded headers from each relevant interface. Retain lockfile changes, deployed package versions, proxy settings and access-control test results.
Last verified: 2026-11-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | @fastify/proxy-addr and Fastify trustProxy configurations |
|---|---|
| Advisory | GHSA-fmr2-3fr5-78g8 |
| CVE | CVE-2026-121192 |
| Authoritative release date | 2026-11-16T09:34:49Z — earliest project advisory in this group; individual publication times are listed below. |
| Authority revision date | No separate material advisory revision is confirmed. |
| Affected versions | @fastify/proxy-addr 3.0.0 through 5.1.2 when trustProxy uses a zoned IPv6 link-local address on a multi-homed host; an attacker must be on another directly connected link. |
| Fixed version | @fastify/proxy-addr 5.1.3 or later |
| CVSS base score | 6.8 (CVSS v3.1) |
| CVSS severity | Moderate |
| Exploitation status | The cited Fastify project advisories do not confirm exploitation in the wild.; no exploitation claim is inferred. |
What Changed
The project disclosed a trust check that ignored IPv6 zone identifiers. A host on another local link with the same link-local address could be trusted as the proxy and supply forwarded client, host and protocol values.
Advisory-Specific Version Boundaries
| <a href="https://github.com/fastify/proxy-addr/security/advisories/GHSA-fmr2-3fr5-78g8">CVE-2026-121192</a> | Affected: >= 3.0.0, < 5.1.3. Fixed: 5.1.3. CVSS v3.1: 6.8; Moderate. Published: 2026-11-16T09:34:49Z. |
|---|
What To Validate Now
- Inventory. Record resolved proxy-addr versions, trustProxy values, network interfaces and controls that rely on request.ip, request.ips, request.host or request.protocol.
- Establish applicability. The default trustProxy: false and global, private or loopback proxy addresses are outside this specific flaw. Verify the configured zone and whether untrusted hosts can reach another local link.
- Remediate. Install 5.1.3 or later and redeploy the resolved dependency. If deployment must wait, use a suitable global, private or loopback proxy address, or restrict reachability to the intended proxy link.
- Validate. Test accepted and rejected forwarded headers from each relevant interface. Retain lockfile changes, deployed package versions, proxy settings and access-control test results.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Link-local traffic is not routed; this advisory does not establish an internet-reachable bypass. Unzoned link-local trust entries remain zone-agnostic by design, so upgrading does not replace deliberate proxy configuration.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

