CVE-2011-3639: Apache HTTP Server mod_proxy Reverse-Proxy SSRF
- Vendor
- Apache Software Foundation
CVE-2011-3639 is an incomplete-fix vulnerability in Apache HTTP Server mod_proxy affecting Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x before 2.2.18 when the Revision 1179239 patch for CVE-2011-3368 is present. The flaw arises from improper interaction between reverse-proxy configuration using RewriteRule or ProxyPassMatch pattern matching and HTTP/0.9 requests containing a malformed URI that begins with an at-sign character. An unauthenticated remote client can cause the reverse proxy to forward requests to intranet hosts.
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.
An external attacker can use the affected server as a server-side request forgery proxy to issue requests to internal or otherwise network-restricted servers. This can expose internal services to attacker-controlled requests and may enable access to internal resources reachable by the Apache server.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid or restrict vulnerable reverse-proxy configurations that use RewriteRule or ProxyPassMatch pattern matching. Enforce rejection of HTTP/0.9 requests and malformed request targets at the edge, and limit the reverse proxy's network access to internal destinations using network segmentation and egress filtering.
Remediation
Patch, then assume compromise.
Upgrade Apache HTTP Server to version 2.2.18 or a vendor-supported release containing the fix for CVE-2011-3639. Apache HTTP Server 2.0.x is end of life; migrate to a supported release and apply the vendor-provided security update.
Exploits
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2011-3639 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2011-3639 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2011-3639?
- As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2011-3639. 1 candidate exploit record is not yet analyzed.
- Is there a patch for CVE-2011-3639?
- Upgrade Apache HTTP Server to version 2.2.18 or a vendor-supported release containing the fix for CVE-2011-3639. Apache HTTP Server 2.0.x is end of life; migrate to a supported release and apply the vendor-provided security update.
- What products are affected by CVE-2011-3639?
- Apache Software Foundation Apache HTTP Server, Apache Software Foundation Http Server2.0a1, Apache Software Foundation Http Server2.0a2, Apache Software Foundation Http Server2.0a3, Apache Software Foundation Http Server2.0a4, and 5 more.
- How severe is CVE-2011-3639?
- CVE-2011-3639 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 49.7% (99th percentile) as of Oct 16, 2026.
Recent activity
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.