VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

openssl: vulnerability history, versions and safety

openssl is a package in the OSS-Fuzz ecosystem. Vulert records 10 vulnerabilities for it across 7 releases, from Jun 2020 to Jul 2024. 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 M2 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all openssl vulnerabilities

Vulert verdict on openssl i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 13 Jul 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 4 years · 0 in the last year i
  • Latest disclosure 13 Jul 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 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 openssl, 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 7 of 7 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 5
  • 2021 2
  • 2024 3

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

03 Vulnerabilities

Recorded vulnerabilities for openssl

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-use-after-free in openssl:ssl_get_prev_session N/A high 5f96a95e2562f026557f625e50c052e77c7bc2e8 13 Jan 2021
Heap-buffer-overflow in openssl: asn1_ex_i2c N/A medium 0df65d82dbc41e8da00adb243de5918db532c8a6 13 Jan 2021
Heap-use-after-free in CRYPTO_DOWN_REF in OpenSSL N/A high fe56d5951f0b42fd3ff1cf42a96d07f06f9692bc 24 Jun 2020
Heap-use-after-free vulnerability in OpenSSL N/A high fe56d5951f0b42fd3ff1cf42a96d07f06f9692bc 24 Jun 2020
Heap-buffer-overflow in OPENSSL_strlcpy N/A high 036913b1076da41f257c640a5e6230476c647eff 01 Jul 2020

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 openssl

Is openssl safe to use?

Vulert records 10 vulnerabilities for openssl in OSS-Fuzz: 0 critical, 4 high, 2 medium and 0 low, plus 4 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.

How many vulnerabilities does openssl have?

10 vulnerabilities are recorded for openssl in the OSS-Fuzz ecosystem: 0 critical, 4 high, 2 medium and 0 low, plus 4 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 openssl vulnerabilities disclosed?

0 vulnerabilities were recorded for openssl in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. 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 openssl 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 openssl for upcoming vulnerabilities?

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