Public proof of concept

CVE-2016-0800

Q: Is CVE-2016-0800 actively exploited?

Active exploitation of CVE-2016-0800 has not been confirmed. Its EPSS score was 82.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2016-0800?

CVE-2016-0800 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.

A public proof of concept exists; no exploitation attested.

Published2016-03-01
WeaknessCWE-200 · CWE-310

Am I 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

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.

Timeline

dates in UTC

2016-03-0120:59CVE 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 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-0800?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-0800?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

OpenSSL

Branch	Affected	Fixed in	Source
1.0	= 1.0.1	no fix published	NVD
1.0	= 1.0.1a	no fix published	NVD
1.0	= 1.0.1b	no fix published	NVD
1.0	= 1.0.1c	no fix published	NVD
1.0	= 1.0.1d	no fix published	NVD
1.0	= 1.0.1e	no fix published	NVD
1.0	= 1.0.1f	no fix published	NVD
1.0	= 1.0.1g	no fix published	NVD
1.0	= 1.0.1h	no fix published	NVD
1.0	= 1.0.1i	no fix published	NVD
1.0	= 1.0.1j	no fix published	NVD
1.0	= 1.0.1k	no fix published	NVD

Pulsesecure client

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

Pulsesecure steel belted radius

Branch	Affected	Fixed in	Source
—	all versions	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

ICSA-16-103-03C CISA6 known affected
Siemens Industrial Products DROWN Vulnerability (Update C)
Siemens SCALANCE X300 family: <V4.1.0 · Siemens SCALANCE X414: <V3.10.2 · Siemens SCALANCE X200 IRT family: <V5.3.0 · +3 more

Full record on NVD

Fix

Mitigation from the vendor CISA ICSA-16-103-03C · 6 productsSiemens has released updates and encourages users to apply them as soon as possible. The following is a list of the products with their corresponding updates.
Mitigation from the vendor CISA ICSA-16-103-03C · 6 productsSCALANCE X300 family: Update to V4.1.0: (https://support.industry.siemens.com/cs/ww/en/view/109748080)
Mitigation from the vendor CISA ICSA-16-103-03C · 6 productsSCALANCE X414: Update to V3.10.2: (https://support.industry.siemens.com/cs/ww/en/view/109747276)
Mitigation from the vendor CISA ICSA-16-103-03C · 6 productsSCALANCE X200 IRT family: Update to V5.3.0: (https://support.industry.siemens.com/cs/document/109744096)
Mitigation from the vendor CISA ICSA-16-103-03C · 6 productsSCALANCE X200 RNA family: Update to V3.2.5: (https://support.industry.siemens.com/cs/ww/en/view/109745413)
Mitigation from the vendor CISA ICSA-16-103-03C · 6 productsSCALANCE X200 family: Update to V5.2.2: (https://support.industry.siemens.com/cs/ww/de/view/109752018)

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 1 repository, unverifiedanthophilee/A2SV--SSL-VUL-Scan

Sources

NVDCVSS 3.05.9read 2026-10-23
NVDCVSS 2.04.3read 2026-10-23
NVDweakness (CWE)CWE-200, CWE-310read 2026-10-23
FIRST EPSSEPSS score82.1 %read 2026-10-23
PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Published: 2016-03-01
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2016-0800?

Is CVE-2016-0800 actively exploited?

Active exploitation of CVE-2016-0800 has not been confirmed. Its EPSS score was 82.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-0800?

CVE-2016-0800 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.

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 ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

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.

Back to CVE Database