CVE-2016-0800

HIGHNVD 5.98.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.8 because EPSS predicts 82% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 82%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 82%CVSS: 5.9Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA data, which makes it easier for remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a "DROWN" attack.

CVSS v3
5.9
EG Score
8.8(high)
EG Risk
77(Track)
EG Risk 77/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
Severity88% × 45%
Exploitation82% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
82%
EPSS %ILE
100%
KEV
Not listed

Published

March 1, 2016

Last Modified

June 17, 2026

References (126)

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2016-07-27redhat
redhatopenssl2016-03-22redhat
redhatpatch2016-03-14redhat
redhatpatch2016-03-14redhat
redhatrhev-hypervisor7-0:7.2-20160302.1.el7ev2016-03-09redhat
redhatopenssl098e-0:0.9.8e-29.el7_2.32016-03-09redhat
redhatopenssl-0:1.0.1e-16.el6_5.162016-03-01redhat
redhatopenssl-1:1.0.1e-42.ael7b_1.102016-03-01redhat
redhatopenssl-0:0.9.7a-43.23.el42016-03-01redhat
redhatopenssl-0:0.9.8e-39.el5_112016-03-01redhat
redhatopenssl-0:0.9.8e-26.el5_9.52016-03-01redhat
redhatopenssl-1:1.0.1e-51.el7_2.42016-03-01redhat

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

(8 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
nss—3.13—
openssl—1.0.0c-2—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
nss—3.13—
openssl—1.0.0c-2—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
nss—3.13—
openssl—1.0.0c-2—
Debian:14(2)
PackageVulnerable rangeFixed inDependents
nss—3.13—
openssl—1.0.0c-2—

Weakness Classification(2)

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

All Vendor Advisories

(12)

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

Publicly available exploits

(2 references)

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

  • GitHub PoCanthophilee/A2SV--SSL-VUL-Scan
    First seen Jan 1, 2021

    A2SV = Auto Scanning to SSL Vulnerability HeartBleed, CCS Injection, SSLv3 POODLE, FREAK... etc Support Vulnerability [CVE-2007-1858] Anonymous Cipher [CVE-2012-4929] CRIME(SPDY) [CVE-2014-0160] CCS Injection [CVE-2014-0224] HeartBleed [CVE-2014-3566] SSLv3 POODLE [CVE-2015-0204] FREAK Attack [CVE-2015-4000] LOGJAM Attack [CVE-2016-0800] SSLv2 DROWN Installation : $ apt update && apt upgrade $ apt install git $ apt install python2 $ apt install python $ git clone https://github.com/hahwul/ a2sv $ cd a2sv $ chmod +x * $ pip2 install -r requirements.txt usage : $ python2 a2sv.py -h It shows all commands how we can use this tool $ python a2sv.py -t 127.0.0.1 127.0.0.1 = target means here own device

    Open source ↗
  • Metasploitauxiliary/scanner/ssl/ssl_version✓ verified
    First seen Oct 14, 2014

    SSL/TLS Version Detection

    Open source ↗

Frequently asked(5)

What is CVE-2016-0800?
CVE-2016-0800 is a high vulnerability published on March 1, 2016. The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to send a ServerVerify message before establishing that a client possesses certain plaintext RSA data, which makes it easier for remote attackers to decrypt TLS ciphertext data by…
When was CVE-2016-0800 disclosed?
CVE-2016-0800 was first published in the National Vulnerability Database on March 1, 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-0800 actively exploited?
CVE-2016-0800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82% 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-0800?
CVE-2016-0800 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
How do I remediate CVE-2016-0800?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-0800, 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-0800

Explore →

Is Your Infrastructure Affected by CVE-2016-0800?

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

Start Free Scan →Browse All CVEs