CVE-2016-5387

What it is

The Apache HTTP Server through 2.4.23 follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue. NOTE: the vendor states "This mitigation has been assigned the identifier CVE-2016-5387"; in other words, this is not a CVE ID for a vulnerability.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

55.7% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2016-07-19 02:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:49 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 55.7% in the next 30 days (EPSS).
• Severity: 8.1 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2016-07-19 02:00 UTC

Last modified

2026-06-17 00:49 UTC

Exploit probability

55.7% · EPSS, next 30 days

Record status

Modified

Affected

• Apache Http Server ≤ 2.2.31
• Apache Http Server ≤ 2.4.23
• HP System Management Homepage ≤ 7.5.5.0
• Oracle Communications User Data Repository ≤ 12.4
• Oracle Enterprise Manager Ops Center 12.2.2
• Oracle Enterprise Manager Ops Center 12.3.2
• Oracle Linux 5
• Oracle Linux 6

Attack profile CVSS 3.1 · 8.1

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-5387.md and follow it. Check whether this project is affected by CVE-2016-5387. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge