CVE-2016-10931

CVE-2016-10931 is a high-severity vulnerability in Rust-openssl Project Rust-openssl with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-295.

Key facts

Description

An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification.

Frequently asked questions

What is CVE-2016-10931?
An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification.
How severe is CVE-2016-10931?
CVE-2016-10931 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-10931 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-10931?
CVE-2016-10931 affects Rust-openssl Project Rust-openssl. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-10931?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-10931 published?
CVE-2016-10931 was published on 2019-08-26 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Rust-openssl Project Rust-openssl

All CVEs affecting Rust-openssl Project Rust-openssl →

Other CWE-295 (Improper Certificate Validation) vulnerabilities

Browse all CWE-295 (Improper Certificate Validation) vulnerabilities →