Pyopenssl
5 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Pyopenssl, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Pyopenssl CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 2 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 5 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical1
- High1
- Medium3
Latest CVEs
The 5 most recently published vulnerabilities affecting Pyopenssl.
- CVE-2026-27459pyOpenSSL DTLS cookie callback buffer overflow9.8
- CVE-2026-27448pyOpenSSL allows TLS connection bypass via unhandled callback exception in set_tlsext_servername_callback5.3
- CVE-2018-1000808Python Cryptographic Authority pyopenssl version Before 17.5.0 contains a CWE - 401 : Failure to Release Memory Before Removing Last Reference vulnerability in PKCS #12 Store that can result in Den...5.9
- CVE-2018-1000807Python Cryptographic Authority pyopenssl version prior to version 17.5.0 contains a CWE-416: Use After Free vulnerability in X509 object handling that can result in Use after free can lead to possi...8.1
- CVE-2013-4314The X509Extension in pyOpenSSL before 0.13.1 does not properly handle a '\0' character in a domain name in the Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle...4.3
Product grouping is registry-driven, with AI assist and human review. How it works