CVE-2016-5387

HIGHNVD 8.18.5▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.5 because EPSS predicts 56% probability of exploitation within the next 30 days (top 1.1% of all CVEs). NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 385 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 56%
CISA-KEV: Not listedEPSS PROB: 56%CVSS: 8.1Exploit: Elevated riskExposed: 385

A fix is available — apply it.

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.

Live · internet exposure

385 internet-exposed hosts are running an affected version of CVE-2016-5387 right now.

across 52 countries (United States, Japan, Germany, France, Italy)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
8.1
EG Score
8.5(high)
EG Risk
65(Track)
EG Risk 65/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation56% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
56%
EPSS %ILE
99%
KEV
Not listed

Published

July 19, 2016

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Sep 9, 2026
No patch confirmed yet. Sources: cert.
cert

VU#797896 - CGI web servers assign Proxy header values from client requests to internal HTTP_PROXY environment variables

http://www.kb.cert.org/vuls/id/797896
generic

[SECURITY] [DSA 3623-1] apache2 security update

http://www.debian.org/security/2016/dsa-3623
generic
http://rhn.redhat.com/errata/RHSA-2016-1649.html
generic
http://rhn.redhat.com/errata/RHSA-2016-1648.html

Vendor Advisories for CVE-2016-5387(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.18-2ubuntu3.1) @ xenial2026-05-22ubuntu
redhatjbcs-httpd24-httpd-0:2.4.6-77.SP1.jbcs.el72016-09-12redhat
redhatpatch2016-08-22redhat
redhattomcat-native-0:1.1.34-5.redhat_1.ep6.el72016-08-22redhat
redhattomcat-native-0:1.1.34-5.redhat_1.ep6.el62016-08-22redhat
redhattomcat8-0:8.0.18-62_patch_01.ep7.el72016-08-18redhat
redhattomcat8-0:8.0.18-62_patch_01.ep7.el62016-08-18redhat
redhatpatch2016-08-17redhat
redhatpatch2016-08-17redhat
redhathttpd24-httpd-0:2.4.18-11.el72016-07-18redhat
redhathttpd-0:2.4.6-40.el7_2.42016-07-18redhat
redhathttpd-0:2.2.15-54.el6_82016-07-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
apache22.2.16-r0 ... 2.4.9-r1 (52 versions)2.4.23-r1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.23-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.23-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.23-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.23-2—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
apache22.2.22-13 ... 2.2.22-13+deb7u6 (7 versions)2.2.22-13+deb7u7—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
apache22.4.10-10, 2.4.10-10+deb8u1, 2.4.10-10+deb8u2, 2.4.10-10+deb8u3, 2.4.10-10+deb8u42.4.10-10+deb8u5—

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 110 total refreshes for this CVE.

  1. 2026-09-18 23:23 UTCOSV refresh
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-17 19:21 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-13 16:41 UTCEPSS rescore
  6. 2026-09-12 14:55 UTCEPSS rescore
  7. 2026-09-10 09:26 UTCEPSS rescore
  8. 2026-09-04 13:56 UTCEPSS rescore
  9. 2026-09-02 14:07 UTCEPSS rescore
  10. 2026-08-31 03:02 UTCOSV refresh
  11. 2026-08-30 19:12 UTCEPSS rescore
  12. 2026-08-26 14:41 UTCEPSS rescore
  13. 2026-08-25 13:44 UTCEPSS rescore
  14. 2026-08-23 00:13 UTCEPSS rescore
  15. 2026-08-21 23:44 UTCEPSS rescore
  16. 2026-08-19 16:59 UTCEPSS rescore
  17. 2026-08-18 13:43 UTCEPSS rescore
  18. 2026-08-17 13:42 UTCEPSS rescore
  19. 2026-08-16 14:51 UTCEPSS rescore
  20. 2026-08-16 02:09 UTCEPSS rescore
  21. 2026-08-15 01:25 UTCEPSS rescore
  22. 2026-08-14 11:15 UTCOSV refresh
  23. 2026-08-12 13:46 UTCEPSS rescore
  24. 2026-08-11 13:36 UTCEPSS rescore
  25. 2026-08-06 13:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-01 04:11 UTCEPSS rescore
  2. 2026-07-30 16:23 UTCEPSS rescore
  3. 2026-07-30 01:26 UTCEPSS rescore
  4. 2026-07-29 22:07 UTCOSV refresh
  5. 2026-07-28 15:31 UTCEPSS rescore
  6. 2026-07-26 14:50 UTCEPSS rescore
  7. 2026-07-25 14:13 UTCEPSS rescore
  8. 2026-07-23 01:23 UTCEG score recompute▲ 0.40
  9. 2026-07-22 22:02 UTCEG score recompute
  10. 2026-07-22 14:04 UTCEPSS rescore
  11. 2026-07-21 15:21 UTCEPSS rescore
  12. 2026-07-21 15:21 UTCEPSS rescore
  13. 2026-07-20 17:03 UTCEPSS rescore
  14. 2026-07-19 14:27 UTCEPSS rescore
  15. 2026-07-19 02:26 UTCEPSS rescore
  16. 2026-07-19 02:26 UTCEPSS rescore
  17. 2026-07-16 16:59 UTCEPSS rescore
  18. 2026-07-16 16:59 UTCEPSS rescore
  19. 2026-07-15 16:54 UTCEPSS rescore
  20. 2026-07-15 16:54 UTCEPSS rescore
  21. 2026-07-13 22:26 UTCEPSS rescore
  22. 2026-07-13 06:09 UTCEPSS rescore
  23. 2026-07-12 08:38 UTCOSV refresh
  24. 2026-07-12 05:43 UTCEPSS rescore
  25. 2026-07-12 05:43 UTCEPSS rescore
  26. 2026-07-11 08:23 UTCEPSS rescore
  27. 2026-07-09 19:05 UTCEPSS rescore
  28. 2026-07-08 15:10 UTCEPSS rescore
  29. 2026-07-05 02:27 UTCEPSS rescore
  30. 2026-07-04 06:28 UTCEPSS rescore
  31. 2026-07-01 15:02 UTCEPSS rescore
  32. 2026-06-30 23:19 UTCEPSS rescore
  33. 2026-06-28 04:53 UTCEPSS rescore
  34. 2026-06-27 03:05 UTCEPSS rescore
  35. 2026-06-27 03:05 UTCEPSS rescore
  36. 2026-06-25 13:47 UTCEPSS rescore
  37. 2026-06-25 13:47 UTCEPSS rescore
  38. 2026-06-24 14:02 UTCEPSS rescore
  39. 2026-06-24 14:02 UTCEPSS rescore
  40. 2026-06-23 21:30 UTCEPSS rescore
  41. 2026-06-23 14:20 UTCOSV refresh
  42. 2026-06-21 01:57 UTCEPSS rescore
  43. 2026-06-21 01:57 UTCEPSS rescore
  44. 2026-06-18 17:50 UTCEPSS rescore
  45. 2026-06-17 17:50 UTCEPSS rescore
  46. 2026-06-17 17:50 UTCEPSS rescore
  47. 2026-06-16 17:50 UTCEPSS rescore
  48. 2026-06-16 17:50 UTCEPSS rescore
  49. 2026-06-15 17:45 UTCEPSS rescore
  50. 2026-06-14 23:14 UTCEPSS rescore
  51. 2026-06-12 23:09 UTCEPSS rescore
  52. 2026-06-12 23:09 UTCEPSS rescore
  53. 2026-06-11 13:57 UTCEPSS rescore
  54. 2026-06-10 22:15 UTCEPSS rescore
  55. 2026-06-10 13:18 UTCEPSS rescore
  56. 2026-06-06 17:29 UTCOSV refresh
  57. 2026-06-06 13:45 UTCEPSS rescore
  58. 2026-06-05 22:44 UTCEPSS rescore
  59. 2026-06-05 06:08 UTCEPSS rescore
  60. 2026-06-05 06:08 UTCEPSS rescore
  61. 2026-06-04 13:10 UTCEPSS rescore
  62. 2026-06-04 13:10 UTCEPSS rescore
  63. 2026-06-02 20:10 UTCEPSS rescore
  64. 2026-06-01 13:49 UTCEPSS rescore
  65. 2026-06-01 13:49 UTCEPSS rescore
  66. 2026-05-31 22:28 UTCEPSS rescore
  67. 2026-05-31 22:28 UTCEPSS rescore
  68. 2026-05-31 00:14 UTCEPSS rescore
  69. 2026-05-29 13:41 UTCEPSS rescore
  70. 2026-05-28 13:42 UTCEPSS rescore
  71. 2026-05-28 13:42 UTCEPSS rescore
  72. 2026-05-27 13:38 UTCEPSS rescore
  73. 2026-05-27 13:38 UTCEPSS rescore
  74. 2026-05-24 16:43 UTCEPSS rescore
  75. 2026-05-22 21:15 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2016-5387?
CVE-2016-5387 is a high vulnerability published on July 19, 2016. 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…
When was CVE-2016-5387 disclosed?
CVE-2016-5387 was first published in the National Vulnerability Database on July 19, 2016, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-5387 actively exploited?
CVE-2016-5387 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 56% probability of exploitation in the next 30 days, which ranks it in the top 1.0% of all scored CVEs.
What is the CVSS score of CVE-2016-5387?
CVE-2016-5387 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2016-5387?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-5387, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-5387

Explore →

Is Your Infrastructure Affected by CVE-2016-5387?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs