Vulnerability Database · Debian · libgcrypt11 · Version
libgcrypt11 1.5.0-5
1.5.0-5 is affected by 5 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 0 Low 0 Unrated 5
-
Database updated 23/Oct/2026
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 Vulnerabilities affecting this version
libgcrypt11 1.5.0-5 vulnerabilities
5 vulnerabilities cover libgcrypt11 1.5.0-5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Key Disclosure Vulnerability in libgcrypt11 | N/A unrated | 1.5.0-5+deb7u6 | 06 Jul 2017 |
| Vulnerability in libgcrypt11 - Security Update | N/A unrated | 1.5.0-5+deb7u5 | 23 Aug 2016 |
| Vulnerability in libgcrypt11 - Security Update | N/A unrated | 1.5.0-5+deb7u4 | 15 Feb 2016 |
| Security Update for libgcrypt11 | N/A unrated | 1.5.0-5+deb7u3 | 12 Mar 2015 |
| Vulnerability in libgcrypt11 - Elgamal Encryption Subkeys Leakage | N/A unrated | 1.5.0-5+deb7u2 | 16 Nov 2014 |
Looking for another version, or everything Vulert holds for libgcrypt11?
Questions
About libgcrypt11 1.5.0-5
Is libgcrypt11 1.5.0-5 vulnerable?
Yes. 5 vulnerabilities in the Vulert database cover libgcrypt11 1.5.0-5: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. Each entry above names the fixed version to move to.
How do I monitor libgcrypt11 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libgcrypt11 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.