VulertSecurity VulertSecurity

Vulnerability Database · Ubuntu · Package report

libcrypto++: vulnerability history, versions and safety

libcrypto++ is a package in the Ubuntu ecosystem. Vulert records 10 vulnerabilities for it across 4 releases, from Sep 2016 to May 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 U10
i
9 with no fix published

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

See the unfixed vulnerabilities →
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 libcrypto++ vulnerabilities

Vulert verdict on libcrypto++ i

Updated on 23 Oct 2026

Careful: 9 of the 10 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 10 vulnerabilities on record across 7 years, none in the last year.

What to do: Plan around the 9 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 10 over 7 years · 0 in the last year i
  • Latest disclosure 14 May 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 9 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 libcrypto++, 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.

i
Version Vulert vulnerabilities Fix published Details
5.6.1-6 U10 No Details →
5.6.1-6+deb8u3build0.14.04.1 U10 No Details →
5.6.1-6+deb8u3ubuntu0.1~esm1 U9 No Details →
5.6.1-6+deb8u1build0.14.04.1 U10 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 1
  • 2019 1
  • 2021 3
  • 2023 4
  • 2024 1

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 libcrypto++

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Fault Injection Vulnerability in libcrypto++ Package 9.8 critical No fix published 14 May 2024
Critical Timing Side Channel Vulnerability in libcrypto++ Package 7.5 high No fix published 22 Aug 2023
Denial of Service Vulnerability in libcrypto++: CVE-2023-50980 7.5 high No fix published 18 Dec 2023
Denial of Service Vulnerability in libcrypto++: CVE-2023-50981 7.5 high No fix published 18 Dec 2023
Sensitive Information Exposure in Crypto++ Package - CVE-2016-7420 5.9 medium No fix published 16 Sep 2016

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 libcrypto++

Is libcrypto++ safe to use?

Vulert records 10 vulnerabilities for libcrypto++ in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 10 not yet rated. 9 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libcrypto++ have?

10 vulnerabilities are recorded for libcrypto++ in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 libcrypto++ vulnerabilities disclosed?

0 vulnerabilities were recorded for libcrypto++ in the last 12 months, and the oldest entry in this database dates to 16 Sep 2016. 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 libcrypto++ 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 libcrypto++ for upcoming vulnerabilities?

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