CVE-2016-8610
A public proof of concept exists; no exploitation attested.
- Published2017-11-13
- WeaknessCWE-400
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2017-11-1322:29CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-8610?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-8610?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 11.2 | = 11.2.0.4 | no fix published | NVD |
| 12.1 | = 12.1.0.2 | no fix published | NVD |
| 12.2 | = 12.2.0.1 | no fix published | NVD |
| 18.x | = 18c | no fix published | NVD |
| 19.x | = 19c | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | ≥ 1.0.2, ≤ 1.0.2h | no fix published | NVD |
| 0.9 | = 0.9.8 | no fix published | NVD |
| 1.0 | = 1.0.1 | no fix published | NVD |
| 1.1 | = 1.1.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 10.3 | = 10.3.6.0.0 | no fix published | NVD |
| 12.1 | = 12.1.3.0.0 | no fix published | NVD |
| 12.2 | = 12.2.1.3.0 | no fix published | NVD |
| 12.2 | = 12.2.1.4.0 | no fix published | NVD |
42 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- bugzilla.redhat.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-400read 2026-10-23
- NVDweakness (CWE)CWE-400read 2026-10-23
- FIRST EPSSEPSS score39.7 %read 2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2017-11-13
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-8610?
Is CVE-2016-8610 actively exploited?
What is the CVSS score for CVE-2016-8610?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.