VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

openssl: vulnerability history, versions and safety

openssl is a package in the Debian ecosystem. Vulert records 25 vulnerabilities for it across 31 releases, from Nov -0001 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
25 vulnerabilities recorded U25
i
18 with no fix published

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

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

Most recent disclosure 29 Sep 2026.

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

Careful: 18 of the 25 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 25 vulnerabilities on record across 2026 years, 16 in the last year.

What to do: Plan around the 18 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 25 over 2026 years · 16 in the last year i
  • Latest disclosure 29 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 18 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 31 of 31 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 5
  • 2025 4
  • 2026 16

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

03 Vulnerabilities

Recorded vulnerabilities for openssl

The 5 most severe of 25 vulnerabilities recorded for this package

Search all 25 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
OpenSSL Out-of-Bounds Read and Write Vulnerability - CVE-2026-72897 7.5 high No fix published 29 Sep 2026
OpenSSL QUIC Stack Vulnerability: Resource Flooding via NEW_CONNECTION_ID Frames 7.5 high No fix published 29 Sep 2026
OpenSSL QUIC Stack Connection Flow Control Vulnerability - CVE-2026-75804 5.3 medium No fix published 29 Sep 2026
Timing Side-Channel Vulnerability in OpenSSL on ARM64 and RISC-V Platforms 3.7 low No fix published 29 Sep 2026
Critical Vulnerability in OpenSSL Affects Debian Packages N/A unrated No fix published 30 Nov -0001

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

How many vulnerabilities does openssl have?

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

16 vulnerabilities were recorded for openssl 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 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.