CVE-2016-8745

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 16% (96th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 16%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48 resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not not limited to, session ID and the response body. The bug was first noticed in 8.5.x onwards where it appears the refactoring of the Connector code for 8.5.x onwards made it more likely that the bug was observed. Initially it was thought that the 8.5.x refactoring introduced the bug but further investigation has shown that the bug is present in all currently supported Tomcat versions.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100CISA SSVC

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
16%
EPSS %ILE
96th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2017

Last Modified

June 17, 2026

References (60)

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutomcat8 (8.0.37-1ubuntu0.1) @ yakkety2026-05-22ubuntu
redhattomcat-0:7.0.69-11.el7_32017-04-12redhat
redhattomcat6-0:6.0.24-105.el6_82017-03-15redhat
redhatpatch2017-03-07redhat
redhattomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el72017-03-07redhat
redhattomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el62017-03-07redhat

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

(4 across 3 ecosystems)
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
tomcat77.0.56-3 ... 7.0.56-3+deb8u6 (7 versions)
  • every version up to 7.0.56-3+deb8u7: fixed in 7.0.56-3+deb8u7
—
tomcat88.0.14-1 ... 8.0.14-1+deb8u5 (6 versions)
  • every version up to 8.0.14-1+deb8u6: fixed in 8.0.14-1+deb8u6
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
tomcat77.0.28-4 ... 7.0.28-4+deb7u8 (9 versions)
  • every version up to 7.0.28-4+deb7u9: fixed in 7.0.28-4+deb7u9
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.tomcat:tomcat-util7.0.0 ... 7.0.8 (50 versions)
  • 9.0.0.M1 up to 9.0.0.M14: fixed in 9.0.0.M14
  • 8.5.0 up to 8.5.9: fixed in 8.5.9
  • 8.0.0-RC1 up to 8.0.41: fixed in 8.0.41
  • 7.0.0 up to 7.0.75: fixed in 7.0.75
  • 6.0.16 up to 6.0.50: fixed in 6.0.50
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 / 25× 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 154 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-8745?
CVE-2016-8745 is a high vulnerability published on August 10, 2017. A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48 resulted in the current Processor object being added to the Processor cache multiple times. This in turn…
When was CVE-2016-8745 disclosed?
CVE-2016-8745 was first published on August 10, 2017, 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-8745 actively exploited?
CVE-2016-8745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-8745?
CVE-2016-8745 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2016-8745?
A fix for CVE-2016-8745 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2016-8745?

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

Book a Demo →Browse All CVEs