CVE-2015-2309: Symfony HttpFoundation trusted proxy header spoofing
CVE-2015-2309 affects the Symfony HttpFoundation Request class. When at least one trusted proxy is configured, unsafe request-handling methods can incorrectly trust client-supplied HTTP header values. As a result, header-derived properties exposed by methods such as getPort(), isSecure(), getHost(), and getClientIps() may be influenced by attacker-controlled input rather than only by values inserted by trusted infrastructure. The issue is specifically tied to proxy trust handling in deployments that rely on forwarded headers to reconstruct the original client request context.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A man-in-the-middle attacker positioned between the last trusted proxy and the origin web server can spoof or manipulate forwarded header values that Symfony treats as trusted. This can cause the application to misidentify the request scheme, host, port, or client IP address. Depending on application logic, this may enable security control bypasses based on client IP, incorrect generation or validation of absolute URLs, improper secure/non-secure request handling, host-based trust violations, and downstream authorization or auditing errors.
Mitigation
If you can’t patch tonight, do this now.
Apply the vendor fix by upgrading to a patched version. In the interim, minimize trust in forwarded headers unless they are guaranteed to be inserted and protected by trusted proxy infrastructure, and ensure the web server/application only accepts proxy-derived headers from explicitly trusted upstream systems. Unsupported Symfony branches should be migrated because no vendor workaround or backported fix is described for them.
Remediation
Patch, then assume compromise.
Upgrade Symfony HttpFoundation, or the full Symfony distribution, to a fixed release: 2.3.27, 2.5.11, or 2.6.6, as applicable. Deployments on unsupported branches 2.0.x, 2.1.x, 2.2.x, and 2.4.x should migrate to a maintained branch containing the fix, as those versions do not receive patched releases.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2015-2309 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2015-2309 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2015-2309?
- As of Nov 19, 2026, Mallory has found no public exploit for CVE-2015-2309.
- Is there a patch for CVE-2015-2309?
- Upgrade Symfony HttpFoundation, or the full Symfony distribution, to a fixed release: 2.3.27, 2.5.11, or 2.6.6, as applicable. Deployments on unsupported branches 2.0.x, 2.1.x, 2.2.x, and 2.4.x should migrate to a maintained branch containing the fix, as those versions do not receive patched releases.
Recent activity
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.