VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

wolfssl: vulnerability history, versions and safety

wolfssl is a package in the Debian ecosystem. Vulert records 183 vulnerabilities for it across 40 releases, from Nov -0001 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
183 vulnerabilities recorded U183
i
95 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
74 in the last 12 months

Most recent disclosure 25 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 i

Updated on 23 Oct 2026

Careful: 95 of the 183 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 183 vulnerabilities on record across 2026 years, 74 in the last year.

What to do: Plan around the 95 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 183 over 2026 years · 74 in the last year i
  • Latest disclosure 25 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 95 i

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 holds for wolfssl, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 40 of 40 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 5
  • 2016 10
  • 2017 12
  • 2018 2
  • 2019 28
  • 2020 12
  • 2021 10
  • 2022 14
  • 2023 2
  • 2024 11
  • 2025 11
  • 2026 66

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

03 Vulnerabilities

Recorded vulnerabilities for wolfssl

The 5 most severe of 183 vulnerabilities recorded for this package

Search all 183 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-based Buffer Overflow in wolfSSL 9.8 critical 4.1.0+dfsg-1 16 Jan 2019
Out of Bounds Byte Overwrite in wolfSSL - CVE-2017-2800 9.8 critical 3.12.0+dfsg-1 24 May 2017
Buffer Overflow Vulnerability in wolfSSL 4.0.0: Remote Code Execution Risk 9.8 critical 4.1.0+dfsg-1 23 May 2019
Heap-Based Buffer Over-Read in wolfSSL: CVE-2019-16748 9.8 critical 4.2.0+dfsg-1 24 Sep 2019
Out-of-Bounds Write Vulnerability in wolfSSL Package 9.8 critical 4.6.0-1 06 Jan 2021

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 183 vulnerabilities for wolfssl in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 183 not yet rated. 95 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does wolfssl have?

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

74 vulnerabilities were recorded for wolfssl in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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.