CVE-2016-8610

HIGHNVD 7.57.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.8 because EPSS predicts 40% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 40%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL protocol defined processing of ALERT packets during a connection handshake. A remote attacker could use this flaw to make a TLS/SSL server consume an excessive amount of CPU and fail to accept connections from other clients.

CVSS v3
7.5
EG Score
7.8HIGHhigh confidence
EG Risk
56
EG Risk 56/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
Severity78% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or 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
40%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or 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 public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

November 13, 2017

Last Modified

June 17, 2026

References (56)

Vendor Advisories for CVE-2016-8610(6)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.6) @ xenial2026-05-22ubuntu
ubuntulibgnutls30 (3.5.3-5ubuntu1.1) @ yakkety2026-05-22ubuntu
ubuntulibgnutlsxx27 (2.12.23-12ubuntu2.7) @ trusty2026-05-22ubuntu
redhatopenssl2017-08-21redhat
redhattomcat7-0:7.0.54-25_patch_05.ep6.el72017-08-21redhat
redhattomcat-native-0:1.2.8-10.redhat_10.ep7.el72017-07-25redhat
redhatpatch2017-07-25redhat
redhatjbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el72017-06-28redhat
redhatpatch2017-06-07redhat
redhatjbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el62017-06-07redhat
redhatgnutls-0:2.12.23-21.el62017-03-21redhat
redhatopenssl-1:1.0.1e-60.el7_3.12017-02-20redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2j-1: fixed in 1.0.2j-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2j-1: fixed in 1.0.2j-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2j-1: fixed in 1.0.2j-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2j-1: fixed in 1.0.2j-1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.0.1e-2 ... 1.0.1t-1+deb7u1 (45 versions)
  • every version up to 1.0.1t-1+deb7u2: fixed in 1.0.1t-1+deb7u2
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.0.1k-3 ... 1.0.1t-1+deb8u5 (12 versions)
  • every version up to 1.0.1t-1+deb8u6: fixed in 1.0.1t-1+deb8u6
—

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

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 4× in last 7d / 20× 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 131 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCcujanovic/CVE-2016-8610-PoC
    First seen Dec 27, 2016

    CVE-2016-8610 (SSL Death Alert) PoC

    Open source ↗

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

Frequently asked(5)

What is CVE-2016-8610?
CVE-2016-8610 is a high vulnerability published on November 13, 2017. A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL protocol defined processing of ALERT packets during a connection handshake. A remote attacker could use this flaw to make a TLS/SSL server consume an excessive amount of CPU and fail…
When was CVE-2016-8610 disclosed?
CVE-2016-8610 was first published on November 13, 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-8610 actively exploited?
CVE-2016-8610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-8610?
CVE-2016-8610 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.8 (HIGH).
How do I remediate CVE-2016-8610?
A fix for CVE-2016-8610 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-8610 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2016-8610?

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

Book a Demo →Browse All CVEs