{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "3.0.0"
                  },
                  {
                    "last_affected": "5.1.2"
                  }
                ],
                "source": "DESCRIPTION"
              }
            ]
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "085495cbecc9057fce9c32dd7cc40da64a6ed5d5"
            }
          ],
          "repo": "https://github.com/fastify/proxy-addr",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-fmr2-3fr5-78g8"
  ],
  "database_specific": {
    "cna_assigner": "openjs",
    "cwe_ids": [
      "CWE-290",
      "CWE-697"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/121xxx/CVE-2026-121192.json",
    "unresolved_ranges": [
      {
        "extracted_events": [
          {
            "range": [
              {
                "introduced": "3.0.0"
              },
              {
                "fixed": "5.1.3"
              }
            ],
            "source": "AFFECTED_FIELD",
            "strategy": "StandardRange"
          }
        ]
      }
    ]
  },
  "details": "@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.",
  "id": "CVE-2026-121192",
  "modified": "2026-11-17T20:45:41.465048787Z",
  "published": "2026-11-16T12:55:59.956Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://cna.openjsf.org/security-advisories.html"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/121xxx/CVE-2026-121192.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/fastify/proxy-addr/security/advisories/GHSA-fmr2-3fr5-78g8"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-121192"
    }
  ],
  "schema_version": "1.9.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@fastify/proxy-addr vulnerable to IP spoofing via ignored IPv6 zone identifier"
}