Gnupg Gnupg

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any Gnupg product.

RSS Feeds for Gnupg security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in Gnupg products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by Gnupg Sorted by Most Security Vulnerabilities since 2018

Gnupg11 vulnerabilities

Gnupg Libksba9 vulnerabilities

Gnupg Libgcrypt7 vulnerabilities

Gnupg Gpgme1 vulnerability

Gnupg Vs Desktop1 vulnerability

By the Year

In 2025 there have been 0 vulnerabilities in Gnupg. Last year, in 2024 Gnupg had 1 security vulnerability published. Right now, Gnupg is on track to have less security vulnerabilities in 2025 than it did last year.




Year Vulnerabilities Average Score
2025 0 0.00
2024 1 0.00
2023 2 6.55
2022 2 8.15
2021 3 7.07
2020 2 7.50
2019 2 6.70
2018 5 7.20

It may take a day or so for new Gnupg vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Gnupg Security Vulnerabilities

CVE Date Vulnerability Products
CVE-2024-2236 Mar 06, 2024
Side-Channel Timing Attack in libgcrypt RSA (Bleichenbacher Vulnerability) A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
Libgcrypt
CVE-2022-3219 Feb 23, 2023
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Gnupg
CVE-2022-3515 Jan 12, 2023
A vulnerability was found in the Libksba library due to an integer overflow within the CRL parser A vulnerability was found in the Libksba library due to an integer overflow within the CRL parser. The vulnerability can be exploited remotely for code execution on the target system by passing specially crafted data to the application, for example, a malicious S/MIME attachment.
Vs Desktop
Gnupg
Libksba
And others...
CVE-2022-47629 Dec 20, 2022
Libksba before 1.6.3 is prone to an integer overflow vulnerability in the CRL signature parser. Libksba before 1.6.3 is prone to an integer overflow vulnerability in the CRL signature parser.
Libksba
CVE-2022-34903 Jul 01, 2022
GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line.
Gnupg
CVE-2021-40528 Sep 06, 2021
The ElGamal implementation in Libgcrypt before 1.9.4 The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic libraries, a certain dangerous combination of the prime defined by the receiver's public key, the generator defined by the receiver's public key, and the sender's ephemeral exponents can lead to a cross-configuration attack against OpenPGP.
Libgcrypt
CVE-2021-33560 Jun 08, 2021
Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.
Libgcrypt
CVE-2021-3345 Jan 29, 2021
_gcry_md_block_write in cipher/hash-common.c in Libgcrypt version 1.9.0 has a heap-based buffer overflow when the digest final function sets a large count value _gcry_md_block_write in cipher/hash-common.c in Libgcrypt version 1.9.0 has a heap-based buffer overflow when the digest final function sets a large count value. It is recommended to upgrade to 1.9.1 or later.
Libgcrypt
CVE-2019-14855 Mar 20, 2020
A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.
Gnupg
CVE-2020-8945 Feb 12, 2020
The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free The proglottis Go wrapper before 0.1.1 for the GPGME library has a use-after-free, as demonstrated by use for container image pulls by Docker or CRI-O. This leads to a crash or potential code execution during GPG signature verification.
Gpgme
CVE-2019-13050 Jun 29, 2019
Interaction between the sks-keyserver code through 1.2.0 of the SKS keyserver network Interaction between the sks-keyserver code through 1.2.0 of the SKS keyserver network, and GnuPG through 2.2.16, makes it risky to have a GnuPG keyserver configuration line referring to a host on the SKS keyserver network. Retrieving data from this network may cause a persistent denial of service, because of a Certificate Spamming Attack.
Gnupg
CVE-2019-12904 Jun 20, 2019
In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.) NOTE: the vendor's position is that the issue report cannot be validated because there is no description of an attack
Libgcrypt
CVE-2018-1000858 Dec 20, 2018
GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Disclosure, DoS. This attack appear to be exploitable via Victim must perform a WKD request, e.g. enter an email address in the composer window of Thunderbird/Enigmail. This vulnerability appears to have been fixed in after commit 4a4bb874f63741026bd26264c43bb32b1099f060.
Gnupg
CVE-2018-0495 Jun 13, 2018
Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.
Libgcrypt
CVE-2018-12020 Jun 08, 2018
mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers to spoof the output mainproc.c in GnuPG before 2.2.8 mishandles the original filename during decryption and verification actions, which allows remote attackers to spoof the output that GnuPG sends on file descriptor 2 to other programs that use the "--status-fd 2" option. For example, the OpenPGP data might represent an original filename that contains line feed characters in conjunction with GOODSIG or VALIDSIG status codes.
Gnupg
CVE-2018-9234 Apr 04, 2018
GnuPG 2.2.4 and 2.2.5 does not enforce a configuration in which key certification requires an offline master Certify key, which results in apparently valid certifications GnuPG 2.2.4 and 2.2.5 does not enforce a configuration in which key certification requires an offline master Certify key, which results in apparently valid certifications that occurred only with access to a signing subkey.
Gnupg
CVE-2018-6829 Feb 07, 2018
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
Libgcrypt
CVE-2016-4579 Jun 13, 2016
Libksba before 1.3.4 Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-of-bounds read and crash) via unspecified vectors, related to the "returned length of the object from _ksba_ber_parse_tl."
Libksba
CVE-2016-4574 Jun 13, 2016
Off-by-one error in the append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.4 Off-by-one error in the append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.4 allows remote attackers to cause a denial of service (out-of-bounds read) via invalid utf-8 encoded data. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-4356.
Libksba
CVE-2016-4356 Jun 13, 2016
The append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.3 The append_utf8_value function in the DN decoder (dn.c) in Libksba before 1.3.3 allows remote attackers to cause a denial of service (out-of-bounds read) by clearing the high bit of the byte after invalid utf-8 encoded data.
Libksba
CVE-2016-4355 Jun 13, 2016
Multiple integer overflows in ber-decoder.c in Libksba before 1.3.3 Multiple integer overflows in ber-decoder.c in Libksba before 1.3.3 allow remote attackers to cause a denial of service (crash) via crafted BER data, which leads to a buffer overflow.
Libksba
CVE-2016-4354 Jun 13, 2016
ber-decoder.c in Libksba before 1.3.3 uses an incorrect integer data type, which ber-decoder.c in Libksba before 1.3.3 uses an incorrect integer data type, which allows remote attackers to cause a denial of service (crash) via crafted BER data, which leads to a buffer overflow.
Libksba
CVE-2016-4353 Jun 13, 2016
ber-decoder.c in Libksba before 1.3.3 does not properly handle decoder stack overflows, which ber-decoder.c in Libksba before 1.3.3 does not properly handle decoder stack overflows, which allows remote attackers to cause a denial of service (abort) via crafted BER data.
Libksba
CVE-2014-9087 Dec 01, 2014
Integer underflow in the ksba_oid_to_str function in Libksba before 1.3.2, as used in GnuPG Integer underflow in the ksba_oid_to_str function in Libksba before 1.3.2, as used in GnuPG, allows remote attackers to cause a denial of service (crash) via a crafted OID in a (1) S/MIME message or (2) ECC based OpenPGP data, which triggers a buffer overflow.
Gnupg
Libksba
CVE-2012-6085 Jan 24, 2013
The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet.
Gnupg
CVE-2010-2547 Aug 05, 2010
Use-after-free vulnerability in kbx/keybox-blob.c in GPGSM in GnuPG 2.x through 2.0.16 Use-after-free vulnerability in kbx/keybox-blob.c in GPGSM in GnuPG 2.x through 2.0.16 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a certificate with a large number of Subject Alternate Names, which is not properly handled in a realloc operation when importing the certificate or verifying its signature.
Gnupg
Built by Foundeo Inc., with data from the National Vulnerability Database (NVD). Privacy Policy. Use of this site is governed by the Legal Terms
Disclaimer
CONTENT ON THIS WEBSITE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. Always check with your vendor for the most up to date, and accurate information.