CVE-2016-2183

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 96% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekWeaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 96%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high)
CISA-KEV: Not listedEPSS PROB: 96%CVSS: 7.5Exploit: ssvc poc · epss top5pct · epss highExposed: 0

A fix is available — apply it.

The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a "Sweet32" attack.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
94(Attend)
EG Risk 94/100SSVC: Attend

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
Severity90% × 45%
Exploitation96% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
96%
EPSS %ILE
100%
KEV
Not listed

Published

September 1, 2016

Last Modified

May 29, 2026

References (278)

Vendor Advisories for CVE-2016-2183(20)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-7-source (7u121-2.6.8-1ubuntu0.14.04.3) @ trusty2026-05-22ubuntu
ubuntulibnss3 (2:3.28.4-0ubuntu0.12.04.1) @ precise2026-05-22ubuntu
ubuntulibnss3-tools (2:3.28.4-0ubuntu0.16.04.1) @ xenial2026-05-22ubuntu
ubuntuopenssl (1.0.1f-1ubuntu2.20) @ trusty2026-05-22ubuntu
ubuntuopenjdk-6-jre-lib (6b41-1.13.13-0ubuntu0.12.04.1) @ precise2026-05-22ubuntu
ubuntuopenjdk-8-source (8u121-b13-0ubuntu1.16.04.2) @ xenial2026-05-22ubuntu
redhatopenshift4/ose-machine-config-operator:v4.8.0-202107011817.p0.git.29813c8.assembly.stream2021-07-27redhat
redhatopenshift4/ose-etcd:v4.6.0-202101300140.p02021-02-08redhat
redhatopenshift4/ose-console:v4.5.0-202009201759.p02020-10-01redhat
redhatopenshift3/oauth-proxy:v3.11.170-52020-02-19redhat
redhatopenshift4/ose-oauth-proxy:v4.1.18-2019092019152019-09-27redhat
redhatopenshift3/snapshot-provisioner:v3.11.141-22019-09-03redhat
redhatpatch2019-05-20redhat
redhatpython-0:2.7.5-69.el7_52018-07-03redhat
redhatopenssl2017-11-16redhat
redhatmod_cluster-native-0:1.2.13-9.Final_redhat_2.ep6.el72017-11-16redhat
redhatpatch2017-11-02redhat
redhattomcat7-0:7.0.54-28_patch_05.ep6.el72017-11-02redhat
redhatjbcs-httpd24-openssl-1:1.0.2h-14.jbcs.el72017-09-13redhat
redhatpatch2017-09-13redhat
redhatjbcs-httpd24-openssl-1:1.0.2h-14.jbcs.el62017-09-13redhat
redhatjava-1.7.1-ibm-1:1.7.1.4.1-1jpp.1.el6_82017-05-09redhat
redhatjava-1.8.0-ibm-1:1.8.0.4.1-1jpp.2.el72017-03-08redhat
redhatjava-1.6.0-ibm-1:1.6.0.16.41-1jpp.1.el6_82017-02-28redhat
redhatjava-1.7.0-ibm-1:1.7.0.10.1-1jpp.1.el5_112017-02-28redhat
redhatjava-1.7.1-ibm-1:1.7.1.4.1-1jpp.2.el72017-02-28redhat
redhatopenssl-1:1.0.1e-51.el7_2.72016-09-27redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

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 6× 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.

  1. 2026-07-25 14:13 UTCEPSS rescore
  2. 2026-07-23 01:22 UTCEG score recompute
  3. 2026-07-22 21:21 UTCEG score recompute▲ 1.50
  4. 2026-07-22 21:21 UTCVendor advisory
  5. 2026-07-22 21:20 UTCGHSA enrichment
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-12 08:07 UTCOSV refresh
  8. 2026-07-06 02:20 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-27 03:05 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-23 13:30 UTCOSV refresh
  15. 2026-06-16 17:50 UTCEPSS rescore
  16. 2026-06-16 17:50 UTCEPSS rescore
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-14 23:14 UTCEPSS rescore
  19. 2026-06-13 22:57 UTCEPSS rescore
  20. 2026-06-13 22:57 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-11 13:57 UTCEPSS rescore
  24. 2026-06-10 22:15 UTCEPSS rescore
  25. 2026-06-10 13:18 UTCEPSS rescore
Show 34 more
  1. 2026-06-08 14:14 UTCEPSS rescore
  2. 2026-06-06 15:59 UTCOSV refresh
  3. 2026-06-05 22:44 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-05 06:08 UTCEPSS rescore
  6. 2026-06-04 13:10 UTCEPSS rescore
  7. 2026-06-04 13:10 UTCEPSS rescore
  8. 2026-06-02 20:10 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-05-31 22:28 UTCEPSS rescore
  12. 2026-05-31 22:28 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-29 13:41 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-27 13:38 UTCEPSS rescore
  18. 2026-05-27 13:38 UTCEPSS rescore
  19. 2026-05-26 07:16 UTCEPSS rescore
  20. 2026-05-24 16:43 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-22 18:58 UTCEG score recompute
  24. 2026-05-22 18:58 UTCVendor advisory
  25. 2026-05-22 18:58 UTCGHSA enrichment
  26. 2026-05-22 08:39 UTCOSV refresh
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-20 22:37 UTCEPSS rescore
  29. 2026-05-20 22:37 UTCEPSS rescore
  30. 2026-05-20 11:21 UTCEPSS rescore
  31. 2026-05-20 11:21 UTCEPSS rescore
  32. 2026-05-20 11:21 UTCEPSS rescore
  33. 2026-05-18 21:30 UTCEPSS rescore
  34. 2026-05-18 21:30 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-2183?
CVE-2016-2183 is a critical vulnerability published on September 1, 2016. The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted…
When was CVE-2016-2183 disclosed?
CVE-2016-2183 was first published in the National Vulnerability Database on September 1, 2016, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-2183 actively exploited?
CVE-2016-2183 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
What is the CVSS score of CVE-2016-2183?
CVE-2016-2183 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2016-2183?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2183, 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

Explore the affected products and dependency analysis for CVE-2016-2183

Explore →

Is Your Infrastructure Affected by CVE-2016-2183?

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

Start Free Scan →Browse All CVEs