VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pyopenssl: vulnerability history, versions and safety

pyopenssl is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 74 releases, from Sep 2013 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H4 L1 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 18 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pyopenssl vulnerabilities

Vulert verdict on pyopenssl 26.4.0 i

Updated on 23 Oct 2026

Good news: 26.4.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 10.

Package health score 73/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 26.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 26.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 26.4.0 — unaffected i
  • Vulnerabilities on record 10 over 12 years · 4 in the last year i
  • Latest disclosure 18 Mar 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 4,952 packages i
  • Stars 945 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for pyopenssl, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
26.4.0 01 Aug 2026 none Apache-2.0 — Details →
26.3.0 12 Jun 2026 none Apache-2.0 — Details →
26.2.0 04 May 2026 none Apache-2.0 — Details →
26.1.0 24 Apr 2026 none Apache-2.0 — Details →
26.0.0 15 Mar 2026 none Apache-2.0 — Details →
25.3.0 17 Sep 2025 H1 L1 U2 Apache-2.0 Yes Details →
25.2.0 14 Sep 2025 H1 L1 U2 Apache-2.0 Yes Details →
25.1.0 17 May 2025 H1 L1 U2 Apache-2.0 Yes Details →
25.0.0 12 Jan 2025 H1 L1 U2 Apache-2.0 Yes Details →
24.3.0 27 Nov 2024 H1 L1 U2 Apache-2.0 Yes Details →
24.2.1 20 Jul 2024 H1 L1 U2 Apache-2.0 Yes Details →
24.1.0 09 Mar 2024 H1 L1 U2 Apache-2.0 Yes Details →
24.0.0 23 Jan 2024 H1 L1 U2 Apache-2.0 Yes Details →
23.3.0 26 Oct 2023 H1 L1 U2 Apache-2.0 Yes Details →
23.2.0 31 May 2023 H1 L1 U2 Apache-2.0 Yes Details →
23.1.1 28 Mar 2023 H1 L1 U2 Apache-2.0 Yes Details →
23.1.0 24 Mar 2023 H1 L1 U2 Apache-2.0 Yes Details →
23.0.0 02 Jan 2023 H1 L1 U2 Apache-2.0 Yes Details →
22.1.0 25 Sep 2022 H1 L1 U2 Apache-2.0 Yes Details →
22.0.0 29 Jan 2022 H1 L1 U2 Apache-2.0 Yes Details →
21.0.0 28 Sep 2021 L1 U1 Apache-2.0 Yes Details →
20.0.1 15 Dec 2020 L1 U1 Apache-2.0 Yes Details →
20.0.0 27 Nov 2020 L1 U1 Apache-2.0 Yes Details →
19.1.0 18 Nov 2019 L1 U1 Apache-2.0 Yes Details →
19.0.0 21 Jan 2019 L1 U1 Apache-2.0 Yes Details →
18.0.0 16 May 2018 L1 U1 Apache-2.0 Yes Details →
17.5.0 01 Dec 2017 L1 U1 Apache-2.0 Yes Details →
17.4.0 22 Nov 2017 H2 L1 U3 Apache-2.0 Yes Details →
17.3.0 14 Sep 2017 H2 L1 U3 Apache-2.0 Yes Details →
17.2.0 20 Jul 2017 H2 L1 U3 Apache-2.0 Yes Details →
17.1.0 30 Jun 2017 H2 L1 U3 Apache-2.0 Yes Details →
17.0.0 20 Apr 2017 H2 L1 U3 Apache-2.0 Yes Details →
16.2.0 15 Oct 2016 H2 L1 U3 Apache-2.0 Yes Details →
16.1.0 26 Aug 2016 H2 L1 U3 Apache-2.0 Yes Details →
16.0.0 19 Mar 2016 H2 L1 U3 Apache-2.0 Yes Details →
0.15.1 14 Apr 2015 H2 L1 U3 non-standard Yes Details →
0.15.0 14 Apr 2015 H2 L1 U3 non-standard Yes Details →
0.14.0 23 Feb 2014 H2 L1 U3 non-standard Yes Details →
0.13.1 04 Sep 2013 H2 U2 non-standard Yes Details →
0.13.0 04 Sep 2011 H3 U3 non-standard Yes Details →
0.12.0 12 Apr 2011 H3 U3 non-standard Yes Details →
0.10.0 13 Nov 2009 H3 U3 non-standard Yes Details →
0.9.0 25 Apr 2009 H3 U3 non-standard Yes Details →
0.8.0 29 Dec 2008 H3 U3 non-standard Yes Details →
0.6.0 04 Jun 2008 H3 U3 non-standard Yes Details →
0.7.0 11 Apr 2008 H3 U3 non-standard Yes Details →
0.10-py2.4-win32 — H3 U3 — Yes Details →
0.10-py2.5-win32 — H3 U3 — Yes Details →
0.10-py2.6-win32 — H3 U3 — Yes Details →
0.10.winxp32-py2.4 — H3 U3 — Yes Details →
0.10.winxp32-py2.5 — H3 U3 — Yes Details →
0.10.winxp32-py2.6 — H3 U3 — Yes Details →
0.12-py2.4-win32 — H3 U3 — Yes Details →
0.12-py2.5-win32 — H3 U3 — Yes Details →
0.12-py2.6-win-amd64 — H3 U3 — Yes Details →
0.12-py2.6-win32 — H3 U3 — Yes Details →
0.12-py2.7-win32 — H3 U3 — Yes Details →
0.12-py3.2-win32 — H3 U3 — Yes Details →
0.12.winxp32-py2.5 — H3 U3 — Yes Details →
0.12.winxp32-py2.6 — H3 U3 — Yes Details →
0.12.winxp32-py2.7 — H3 U3 — Yes Details →
0.12.winxp32-py3.2 — H3 U3 — Yes Details →
0.13-py2.4-win32 — H2 U2 — Yes Details →
0.13-py2.5-win32 — H2 U2 — Yes Details →
0.13-py2.6-win32 — H2 U2 — Yes Details →
0.13-py2.7-win32 — H2 U2 — Yes Details →
0.13-py3.2-win32 — H2 U2 — Yes Details →
0.13.1.win-amd64-py2.6 — H3 U3 — Yes Details →
0.13.1.win-amd64-py2.7 — H3 U3 — Yes Details →
0.13.1.win-amd64-py3.2 — H3 U3 — Yes Details →
0.13.1.win32-py2.6 — H3 U3 — Yes Details →
0.13.1.win32-py2.7 — H3 U3 — Yes Details →
0.13.1.win32-py3.2 — H3 U3 — Yes Details →
0.13.winxp32-py2.4 — H3 U3 — Yes Details →
0.13.winxp32-py2.5 — H3 U3 — Yes Details →
0.13.winxp32-py2.6 — H3 U3 — Yes Details →
0.13.winxp32-py2.7 — H3 U3 — Yes Details →
0.13.winxp32-py3.2 — H3 U3 — Yes Details →
0.9.win32-py2.6 — H3 U3 — Yes Details →

All 79 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 1
  • 2018 4
  • 2022 1
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pyopenssl

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27459: pyOpenSSL Buffer Overflow Vulnerability Due to Long Cookie Values 9.8 critical 26.0.0 18 Mar 2026
CVE-2018-1000807: pyopenssl - Use After Free Vulnerability 8.1 high 17.5.0 10 Oct 2018
CVE-2013-4314: PyOpenSSL Mishandles NUL Byte In Certificate Subject Alternative Name 7.5 high 0.13.1 17 May 2022
CVE-2026-27459: pyOpenSSL Buffer Overflow Vulnerability in DTLS Cookie Callback 7.2 high 26.0.0 16 Mar 2026
CVE-2018-1000808: pyopenssl - Failure to Release Memory Before Removing Last Reference 5.9 high 17.5.0 10 Oct 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pyopenssl

Is pyopenssl safe to use?

Vulert records 10 vulnerabilities for pyopenssl in PyPI: 0 critical, 4 high, 0 medium and 1 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is pyopenssl's Vulert package health score?

Vulert scores pyopenssl 73/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of pyopenssl affected?

No. 26.4.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of pyopenssl should I use?

26.4.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does pyopenssl have?

10 vulnerabilities are recorded for pyopenssl in the PyPI ecosystem: 0 critical, 4 high, 0 medium and 1 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pyopenssl vulnerabilities disclosed?

4 vulnerabilities were recorded for pyopenssl in the last 12 months, and the oldest entry in this database dates to 30 Sep 2013. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pyopenssl are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pyopenssl for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pyopenssl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.