CVE-2016-5385

HIGHNVD 8.18.4▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.4EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 50%
CISA-KEV: Not listedEPSS PROB: 50%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

PHP through 7.0.8 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts 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, as demonstrated by (1) an application that makes a getenv('HTTP_PROXY') call or (2) a CGI configuration of PHP, aka an "httpoxy" issue.

CVSS v3
8.1
EG Score
8.4(high)
EG Risk
62(Track)
EG Risk 62/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
Severity84% × 45%
Exploitation50% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
50%
EPSS %ILE
99%
KEV
Not listed

Published

July 19, 2016

Last Modified

May 6, 2026

References (50)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuphp7.0-zip (7.0.8-0ubuntu0.16.04.2) @ xenial2026-05-22ubuntu
redhatphp-0:5.3.3-48.el6_82016-08-11redhat
redhatphp-0:5.4.16-36.3.el7_22016-08-11redhat
redhatphp54-php-0:5.4.40-4.el72016-08-11redhat
redhatphp55-php-0:5.5.21-5.el72016-08-11redhat
redhatrh-php56-php-0:5.6.5-9.el72016-08-11redhat

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

(5 across 1 ecosystem)
Packagist(5)
PackageVulnerable rangeFixed inDependents
amphp/artax2.0.2, v2.0.0, v2.0.1, v2.0.32.0.4—
bugsnag/bugsnag-laravelv1.0.0 ... v2.0.1 (29 versions)2.0.2—
drupal/core8.0.0 ... 8.1.6 (32 versions)8.1.7—
guzzlehttp/guzzle5.0.0 ... 5.3.0 (7 versions)5.3.1—
padraic/humbug_get_contents1.0.0 ... 1.1.1 (7 versions)1.1.2—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 23× 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.

  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-25 14:13 UTCEPSS rescore
  3. 2026-07-23 01:23 UTCEG score recompute▲ 0.30
  4. 2026-07-22 22:02 UTCEG score recompute
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-20 17:03 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-13 22:26 UTCEPSS rescore
  16. 2026-07-13 06:09 UTCEPSS rescore
  17. 2026-07-12 09:07 UTCOSV refresh
  18. 2026-07-11 08:23 UTCEPSS rescore
  19. 2026-07-09 19:05 UTCEPSS rescore
  20. 2026-07-07 13:42 UTCEPSS rescore
  21. 2026-07-04 06:28 UTCEPSS rescore
  22. 2026-07-01 15:02 UTCEPSS rescore
  23. 2026-06-28 04:53 UTCEPSS rescore
  24. 2026-06-27 03:05 UTCEPSS rescore
  25. 2026-06-27 03:05 UTCEPSS rescore
Show 47 more
  1. 2026-06-25 13:47 UTCEPSS rescore
  2. 2026-06-25 13:47 UTCEPSS rescore
  3. 2026-06-24 14:02 UTCEPSS rescore
  4. 2026-06-24 14:02 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-23 14:20 UTCOSV refresh
  7. 2026-06-21 14:54 UTCEPSS rescore
  8. 2026-06-21 14:54 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-18 17:50 UTCEPSS rescore
  12. 2026-06-17 17:50 UTCEPSS rescore
  13. 2026-06-17 17:50 UTCEPSS rescore
  14. 2026-06-16 17:50 UTCEPSS rescore
  15. 2026-06-16 17:50 UTCEPSS rescore
  16. 2026-06-15 17:45 UTCEPSS rescore
  17. 2026-06-14 23:14 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-12 23:09 UTCEPSS rescore
  20. 2026-06-10 22:15 UTCEPSS rescore
  21. 2026-06-10 13:18 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-06 17:29 UTCOSV refresh
  25. 2026-06-05 22:44 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-06-02 20:10 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-29 13:41 UTCEPSS rescore
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-26 07:16 UTCEPSS rescore
  34. 2026-05-24 16:43 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-22 19:29 UTCEG score recompute
  38. 2026-05-22 19:29 UTCVendor advisory
  39. 2026-05-21 22:40 UTCEPSS rescore
  40. 2026-05-20 22:37 UTCEPSS rescore
  41. 2026-05-20 22:37 UTCEPSS rescore
  42. 2026-05-20 22:37 UTCEPSS rescore
  43. 2026-05-20 11:21 UTCEPSS rescore
  44. 2026-05-20 11:21 UTCEPSS rescore
  45. 2026-05-20 11:21 UTCEPSS rescore
  46. 2026-05-18 21:30 UTCEPSS rescore
  47. 2026-05-18 21:30 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2016-5385?
CVE-2016-5385 is a high vulnerability published on July 19, 2016. PHP through 7.0.8 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect applications from the presence of untrusted client data in the HTTPPROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP…
When was CVE-2016-5385 disclosed?
CVE-2016-5385 was first published in the National Vulnerability Database on July 19, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-5385 actively exploited?
CVE-2016-5385 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days, which ranks it in the top 1.2% of all scored CVEs.
What is the CVSS score of CVE-2016-5385?
CVE-2016-5385 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.4.
How do I remediate CVE-2016-5385?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-5385, 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-5385

Explore →

Is Your Infrastructure Affected by CVE-2016-5385?

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

Start Free Scan →Browse All CVEs