PULSE
FEED
ransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcareransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcare
← Todos los CVEs
CVE Watch16 nov 2026

CVE-2026-121192

@fastify/proxy-addr determines which network hops are trusted proxies and backs Fastify's trustProxy setting, so that forwarded headers can

CVSS

6.8

Medio

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 16 nov 2026 · Última mod.: 16 nov 2026 · CWE-290 · CWE-697

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

@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.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1293607.3 ALT
35.9%
——11A weakness has been identified in Linux Foundation Magma up to 1.9.0. The impacted element is an unknown function of the file orc8r/cloud/go/services/obsidian/access/operator.go of the component Obsidian REST. Executing a manipulation of the argument X-Magma-Client-Cert-Serial can lead to authentication bypass by spoofing. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.7h
CVE-2026-124719—
40.6%
——12Authentication bypass by spoofing vulnerability in Apache APISIX. When a Route's configured headers carry a caller identity and the OpenAPI document declares the same header, a caller can act as another identity against the upstream API. This issue affects Apache APISIX: from 3.19.0 before 3.20.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.3d
CVE-2026-124679—
43.1%
——13Authentication bypass by spoofing vulnerability in Apache APISIX. On routes using jwe-decrypt with strict: false and a forward_header distinct from the token header an unauthenticated client can supply the value the upstream treats as gateway-decrypted plaintext. Similar can happen when forward-auth is configured with allow_degradation: true, and the auth service is unavailable. This issue affects Apache APISIX: from 3.18.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.3d
CVE-2026-124666—
37.7%
——11Authentication bypass by spoofing vulnerability in Apache APISIX. On a route where multi-auth falls back from wolf-rbac to another successful authenticator, client-supplied Wolf identity headers can remain in the request. A downstream service that relies on those documented headers may therefore receive an identity that was not established by the successful authenticator. This issue affects Apache APISIX: from 3.8.0 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.3d
CVE-2026-1280237.4 ALT
40.2%
——12FrankenPHP before 1.13.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to spoof trusted headers by sending dot-form header names that PHP rewrites to underscores. Attackers can send headers like X.Authenticated.User or X.Forwarded.For that map to $_SERVER keys, spoofing user identity, client IP, or scheme.4d
CVE-2026-121619—
8.8%
——3The Symfony FrameworkBundle framework.trusted_proxies option and the HttpFoundation Request::setTrustedProxies() method trust remote clients as reverse proxies when the private_ranges shortcut is used, allowing remote attackers to spoof the client IP address, host and scheme in Symfony FrameworkBundle versions 7.1 prior to 7.4.23 and 8.x prior to 8.1.11, and HttpFoundation versions 7.2 prior to 7.4.23 and 8.x prior to 8.1.11. The private_ranges and PRIVATE_SUBNETS keywords resolved to IpUtils::PRIVATE_SUBNETS, the deny list of NoPrivateNetworkHttpClient, which lists the private and special-purpose prefixes a server must not connect to. Since the fix for CVE-2026-48736 (7.4.13 and 8.0.13), this list also covers the IPv6 prefixes that embed an IPv4 address: IPv4-mapped (::ffff:0:0/96), IPv4-compatible (::/96), 6to4 (2002::/16), Teredo (2001::/32) and NAT64 (64:ff9b::/96). The IPv4-mapped entry has been in the list since the private_ranges shortcut was introduced, in 7.1 for framework.trusted_proxies and in 7.2 for Request::setTrustedProxies(). Over-blocking is safe for a deny list, but when the same entries are used as the allow list of trusted proxies, they trust remote clients. A client whose connection arrives with such a source address is treated as a reverse proxy, and the X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto, X-Forwarded-Port and X-Forwarded-Prefix headers it sends are honoured. For example, with Request::setTrustedProxies(['private_ranges'], ...), a request with REMOTE_ADDR set to ::ffff:203.0.113.7 and the headers X-Forwarded-For: 10.0.0.9, X-Forwarded-Host: evil.example.com and X-Forwarded-Proto: https makes getClientIp() return 10.0.0.9, getHost() return evil.example.com and isSecure() return true. Two kinds of deployments are exposed: a server listening on the IPv6 wildcard address without IPV6_V6ONLY reports every IPv4 client in the IPv4-mapped form, so every client is trusted, and a server reachable over IPv6 trusts any client sourcing from 6to4 or Teredo space, which is globally routed, whatever its listener. A spoofed client address defeats IP allow lists, rate limiting and audit logs; a spoofed host poisons the URLs written into password reset and login link e-mails and into shared caches; a spoofed scheme satisfies requires_channel: https over plain HTTP. Symfony 6.4 does not point any trusted proxy setting at IpUtils::PRIVATE_SUBNETS and is not affected by default, but an application that passes that constant to Request::setTrustedProxies() itself could be exposed in the same way on any version. This issue is fixed in 7.4.23 and 8.1.11.4d