How severe is CVE-2016-0800?

CVE-2016-0800 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2016-0800?

Affected package information for CVE-2016-0800 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2016-0800?

No fixed version has been published for CVE-2016-0800 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2016-0800 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2016-0800, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2016-0800 has an EPSS (Exploit Prediction Scoring System) score of 90.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2016-0800?

CVE-2016-0800 is classified as Information Exposure (CWE-200), CWE-310 (CWE-310). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-0800 published, and has it been updated?

CVE-2016-0800 was published on March 1, 2016 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2016-0800

MEDIUM

Published

Mar 1, 2016

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

90.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.…

github.comMetasploitNov 2022

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.…

github.comGithubJan 2021

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-0800 in your stack?

O3 detects CVE-2016-0800 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works