CVE-2026-121619
Awaiting Analysis Awaiting Analysis - Queue

IP Spoofing in Symfony FrameworkBundle via private_ranges

Vulnerability report for CVE-2026-121619, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-12

Last updated on: 2026-11-12

Assigner: Checkmarx

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-12
Last Modified
2026-11-12
Generated
2026-11-12
AI Q&A
2026-11-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 10 associated CPEs
Vendor Product Version / Range
symfony frameworkbundle to 7.4.23 (exc)
symfony httpfoundation to 7.4.23 (exc)
symfony frameworkbundle to 8.1.11 (exc)
symfony httpfoundation to 8.1.11 (exc)
symfony frameworkbundle From 7.1 (inc) to 7.4.23 (exc)
symfony frameworkbundle From 8.0 (inc) to 8.1.11 (exc)
symfony httpfoundation From 7.2 (inc) to 7.4.23 (exc)
symfony httpfoundation From 8.0 (inc) to 8.1.11 (exc)
symfony framework From 7.1 (inc) to 7.4.22 (inc)
symfony framework From 8.0 (inc) to 8.1.10 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-290 This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
CWE-348 The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Symfony FrameworkBundle and HttpFoundation components. It involves the misuse of the private_ranges shortcut and IpUtils::PRIVATE_SUBNETS constant as an allow list for trusted reverse proxies instead of a deny list. Attackers can spoof client IP addresses, host, and scheme by presenting specific IPv6 addresses that embed IPv4 addresses (like IPv4-mapped or 6to4). This allows them to manipulate headers such as X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Proto, bypassing security measures.

Detection Guidance

Check Symfony configuration files for use of private_ranges in trusted_proxies settings. Inspect HTTP headers like X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Proto for suspicious values. Review server logs for requests with IPv4-mapped or IPv6 special addresses (e.g., ::ffff:203.0.113.7). Use commands like grep to search for private_ranges in Symfony configs or logs.

Impact Analysis

This vulnerability can lead to IP spoofing, allowing attackers to bypass IP allow lists, rate limiting, and audit logs. It can also enable host spoofing, which poisons URLs in password reset emails and shared caches. Additionally, attackers can exploit the scheme spoofing to bypass HTTPS requirements, potentially exposing sensitive data or enabling further attacks.

Compliance Impact

This vulnerability can undermine compliance with GDPR and HIPAA by enabling IP spoofing and data breaches. Spoofed IPs can bypass security controls, leading to unauthorized access to personal data. Host spoofing may expose sensitive information in URLs, violating data protection requirements. Organizations must address this issue to maintain compliance with these regulations.

Mitigation Strategies

Update Symfony FrameworkBundle to 7.4.23 or 8.1.11 and HttpFoundation to the same versions. Replace private_ranges with IpUtils::PRIVATE_RANGES in trusted_proxies configurations. Ensure no custom configurations use IpUtils::PRIVATE_SUBNETS for trusted proxies.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-121619. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...