CVE-2016-2108

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
CISA-KEV: Not listedEPSS PROB: 78%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denial of service (buffer underflow and memory corruption) via an ANY field in crafted serialized data, aka the "negative zero" issue.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
80(Track*)
EG Risk 80/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
Severity98% × 45%
Exploitation78% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
78%
EPSS %ILE
100%
KEV
Not listed

Published

May 5, 2016

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

CEC Juniper Community

http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10759

Vendor Advisories for CVE-2016-2108(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.1) @ xenial2026-05-20ubuntu
redhatjbcs-httpd24-openssl-1:1.0.2h-12.jbcs.el62017-01-25redhat
redhatjbcs-httpd24-openssl-1:1.0.2h-12.jbcs.el72017-01-25redhat
redhatpatch2016-12-15redhat
redhatopenssl-0:1.0.1e-42.el6_7.52016-10-18redhat
redhatopenssl2016-10-12redhat
redhatopenssl-0:0.9.8e-40.el5_112016-05-31redhat
redhatopenssl-0:1.0.1e-48.el6_8.12016-05-10redhat
redhatopenssl-1:1.0.1e-51.el7_2.52016-05-09redhat

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 rangeFixed inDependents
openssl—1.0.2c-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2c-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2c-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2c-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1e-2 ... 1.0.1e-2+deb7u9 (21 versions)1.0.1e-2+deb7u21—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1k-3 ... 1.0.1k-3+deb8u4 (6 versions)1.0.1k-3+deb8u5—

Weakness Classification(1)

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

Additional Vendor Advisories

(8)

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-2108?
CVE-2016-2108 is a critical vulnerability published on May 5, 2016. The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denial of service (buffer underflow and memory corruption) via an ANY field in crafted serialized data, aka the "negative zero" issue.
When was CVE-2016-2108 disclosed?
CVE-2016-2108 was first published in the National Vulnerability Database on May 5, 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-2108 actively exploited?
CVE-2016-2108 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2016-2108?
CVE-2016-2108 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-2108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2108, 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-2108

Explore →

Is Your Infrastructure Affected by CVE-2016-2108?

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

Start Free Scan →Browse All CVEs