# CVE-2026-121619: Security feature bypass in symfony

> Remote attackers can spoof trusted reverse proxies using IPv4-mapped, 6to4, Teredo or NAT64 addresses, bypassing Symfony's private_ranges trust shortcut.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`Request::setTrustedProxies()`, `IpUtils::PRIVATE_SUBNETS`)
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-4mg4-f476-cjh5, GHSA-xg2q-4rrq-657q

## What is CVE-2026-121619?

CVE-2026-121619 is a medium-severity security feature bypass vulnerability in sensiolabs symfony, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-348 (Use of Less Trusted Source), CWE-290 (Authentication Bypass by Spoofing)

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

An affected version is only exploitable if your software calls Request::setTrustedProxies() or IpUtils::PRIVATE_SUBNETS. Many projects that include it are not exposed.


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

No fix has been published for CVE-2026-121619 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121619 is a medium-severity security feature bypass vulnerability in sensiolabs symfony, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-121619 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls Request::setTrustedProxies() or IpUtils::PRIVATE_SUBNETS. Many projects that include it are not exposed.

Affected product: sensiolabs symfony. No package-level version data is available, so check the vendor advisory linked from the reference page.

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.
   If an affected version is present, also search the code for calls to Request::setTrustedProxies() or IpUtils::PRIVATE_SUBNETS and report whether any exist.
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-121619/ (Markdown: https://insights.sbomify.com/CVE-2026-121619/index.md)
```

## Sources

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

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