CVE-2016-0701

HIGHNVD 3.78.9▲
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

The DH_check_pub_key function in crypto/dh/dh_check.c in OpenSSL 1.0.2 before 1.0.2f does not ensure that prime numbers are appropriate for Diffie-Hellman (DH) key exchange, which makes it easier for remote attackers to discover a private DH exponent by making multiple handshakes with a peer that chose an inappropriate number, as demonstrated by a number in an X9.42 file.

CVSS v3
3.7
EG Score
8.9HIGHhigh confidence
EG Risk
78
EG Risk 78/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
Severity89% × 45%
Exploitation84% × 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
84%
EPSS %ILE
99th
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

February 15, 2016

Last Modified

June 17, 2026

References (48)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl1.0.0 (1.0.2d-0ubuntu1.3) @ wily2026-05-22ubuntu

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 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2f-2: fixed in 1.0.2f-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2f-2: fixed in 1.0.2f-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2f-2: fixed in 1.0.2f-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2f-2: fixed in 1.0.2f-2
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2016-0701?
CVE-2016-0701 is a high vulnerability published on February 15, 2016. The DHcheckpubkey function in crypto/dh/dhcheck.c in OpenSSL 1.0.2 before 1.0.2f does not ensure that prime numbers are appropriate for Diffie-Hellman (DH) key exchange, which makes it easier for remote attackers to discover a private DH exponent by making multiple handshakes with a peer that chose…
When was CVE-2016-0701 disclosed?
CVE-2016-0701 was first published on February 15, 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-0701 actively exploited?
CVE-2016-0701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-0701?
CVE-2016-0701 has a CVSS v3 base score of 3.7 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9 (HIGH).
How do I remediate CVE-2016-0701?
A fix for CVE-2016-0701 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-0701

Explore →

Is Your Infrastructure Affected by CVE-2016-0701?

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

Book a Demo →Browse All CVEs