VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

wolfssl: vulnerability history, versions and safety

wolfssl is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 18 releases, from Jan 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wolfssl vulnerabilities

Vulert verdict on wolfssl 5.9.2.post0 i

Updated on 23 Oct 2026

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

Package health score 66/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 5.9.2.post0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Stars 42 i
  • Last release 3 months ago i
  • Licence non-standard 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 wolfssl, 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
5.9.2.post0 16 Jul 2026 none non-standard — Details →
5.8.4.post0 30 Dec 2025 none non-standard — Details →
5.8.2.post0 24 Jul 2025 U1 non-standard Yes Details →
5.7.4.post0 13 Nov 2024 U1 non-standard Yes Details →
5.7.2.post0 12 Sep 2024 U1 non-standard Yes Details →
5.6.6.post0 23 Jan 2024 U1 non-standard Yes Details →
5.6.0.post0 02 May 2023 U1 non-standard Yes Details →
5.5.4.post0 30 Dec 2022 U1 non-standard Yes Details →
5.5.3.post0 07 Nov 2022 U1 non-standard Yes Details →
5.4.0.post0 13 Jul 2022 U1 non-standard Yes Details →
5.3.0.post0 13 May 2022 U1 non-standard Yes Details →
4.1.0.post0 27 Sep 2019 U1 non-standard Yes Details →
3.14.0.post1 19 Mar 2018 U1 non-standard Yes Details →
3.13.0.post1 27 Jan 2018 U1 non-standard Yes Details →
3.13.0.post0 09 Jan 2018 U1 non-standard Yes Details →
3.12.2.post0 19 Dec 2017 U1 non-standard Yes Details →
0.1.2 30 Aug 2017 U1 non-standard Yes Details →
0.1.1 23 Aug 2017 U1 non-standard Yes Details →
0.1.0 11 May 2017 U1 non-standard Yes Details →
4.1.0.post0-py3.7-linux-x86_64 — C1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for wolfssl

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-15346: wolfSSL Python Module Improper Authentication Vulnerability 9.3 critical 5.8.4-stable 08 Jan 2026
CVE-2025-15346: wolfSSL Python Module Improper Authentication Vulnerability 9.3 critical 5.8.4.post0 29 Jun 2026

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 wolfssl

Is wolfssl safe to use?

Vulert records 2 vulnerabilities for wolfssl in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 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 wolfssl's Vulert package health score?

Vulert scores wolfssl 66/100, which reads as usable, but worth attention. 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 wolfssl affected?

No. 5.9.2.post0, 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 wolfssl should I use?

5.9.2.post0 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 wolfssl have?

2 vulnerabilities are recorded for wolfssl in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 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 wolfssl vulnerabilities disclosed?

2 vulnerabilities were recorded for wolfssl in the last 12 months, and the oldest entry in this database dates to 08 Jan 2026. 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 wolfssl 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 wolfssl for upcoming vulnerabilities?

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