Gnupg vulnerabilities
59 vulnerabilities
Known vulnerabilities in Gnupg products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 5 products.
Products
5- Gnupg38 vulnerabilities
- Libgcrypt17 vulnerabilities
- Libksba9 vulnerabilities
- Gpg Agent1 vulnerabilities
- Vs Desktop1 vulnerabilities
GCVE-1-2026-0001gnupggnupgReference to the gpg.fail
1. Multiple Plaintext Attack on Detached PGP Signatures in GnuPG - https://gpg.fail/detached
2. GnuPG Accepts Path Separators and Path Traversals in Literal Data "Filename" Field - https://gpg.fail/filename
3. Cleartext Signature Plaintext Truncated for Hash Calculation - https://gpg.fail/formfeed
4. Encrypted message malleability checks are incorrectly enforced causing plaintext recovery attacks - https://gpg.fail/malleability
5. Memory Corruption in ASCII-Armor Parsing - https://gpg.fail/memcpy
6. Trusted comment injection (minisign) - https://gpg.fail/minisign
7. Cleartext Signature Forgery in the NotDashEscaped header implementation in GnuPG - https://gpg.fail/notdash
8. OpenPGP Cleartext Signature Framework Susceptible to Format Confusion - https://gpg.fail/notsoclear
9. GnuPG Output Fails To Distinguish Signature Verification Success From Message Content https://gpg.fail/noverify
10. Cleartext Signature Forgery in GnuPG - https://gpg.fail/nullbyte
11. Radix64 Line-Truncation Enabling Polyglot Attacks - https://gpg.fail/polyglot
12. GnuPG may downgrade digest algorithm to SHA1 during key signature checking - https://gpg.fail/sha1
13. GnuPG Trust Packet Parsing Enables Adding Arbitrary Subkeys - https://gpg.fail/trust
14. Trusted comment Injection (minisign) - https://gpg.fail/trustcommentGCVE-1-2026-0008gnupggpg-agentA crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped
session key (AES Key Wrap ciphertext) can cause a stack buffer overflow in
gpg-agent during PKDECRYPT --kem=CMS handling. The root cause is an
unbounded session key length derived from attacker-controlled ciphertext
and used as the AES Key Wrap output length when decrypting into a
fixed-size stack buffer. libgcrypt’s AES-KW unwrap copies
attacker-controlled bytes into the caller-provided output buffer before
performing integrity checks, so the stack overflow occurs even if later CMS
or key-wrap integrity validation fails.CVE-2018-1000858canonicalubuntu_linux+6
EPSS score1.04%
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.CVE-2018-0495alpinelibgcrypt+27EPSS score0.89%
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.CVE-2018-9234canonicalubuntu_linux+7EPSS score1.96%
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.CVE-2018-6829debiangnupg1+2EPSS score1.78%
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.CVE-2018-12020alpinegnupg+46EPSS score8.25%
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.CVE-2013-4351debiangnupg2+1EPSS score2.52%
GnuPG 1.4.x, 2.0.x, and 2.1.x treats a key flags subpacket with all bits cleared (no usage permitted) as if it has all bits set (all usage permitted), which might allow remote attackers to bypass intended cryptographic protection mechanisms by leveraging the subkey.CVE-2013-4242canonicalubuntu_linux+13EPSS score0.53%
GnuPG before 1.4.14, and Libgcrypt before 1.5.3 as used in GnuPG 2.0.x and possibly other products, allows local users to obtain private RSA keys via a cache side-channel attack involving the L3 cache, aka Flush+Reload.CVE-2013-4402canonicalubuntu_linux+4EPSS score5.03%
The compressed packet parser in GnuPG 1.4.x before 1.4.15 and 2.0.x before 2.0.22 allows remote attackers to cause a denial of service (infinite recursion) via a crafted OpenPGP message.CVE-2013-4576debiangnupg+4EPSS score0.45%
GnuPG 1.x before 1.4.16 generates RSA keys using sequences of introductions with certain patterns that introduce a side channel, which allows physically proximate attackers to extract RSA keys via a chosen-ciphertext attack and acoustic cryptanalysis during decryption. NOTE: applications are not typically expected to protect themselves from acoustic side-channel attacks, since this is arguably the responsibility of the physical device. Accordingly, issues of this type would not normally receive a CVE identifier. However, for this issue, the developer has specified a security policy in which GnuPG should offer side-channel resistance, and developer-specified security-policy violations are within the scope of CVE.CVE-2021-40528alpinelibgcrypt+10EPSS score1.42%
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.CVE-2021-3345ubuntulibgcrypt11+3EPSS score1.06%
_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.CVE-2021-33560alpinelibgcrypt+51EPSS score2.37%
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.CVE-2015-1606debiangnupg2+4EPSS score1.92%
The keyring DB in GnuPG before 2.1.2 does not properly handle invalid packets, which allows remote attackers to cause a denial of service (invalid read and use-after-free) via a crafted keyring file.CVE-2015-1607canonicalubuntu_linux+4EPSS score2.47%
kbx/keybox-search.c in GnuPG before 1.4.19, 2.0.x before 2.0.27, and 2.1.x before 2.1.2 does not properly handle bitwise left-shifts, which allows remote attackers to cause a denial of service (invalid read operation) via a crafted keyring file, related to sign extensions and "memcpy with overlapping ranges."CVE-2015-0837debianlibgcrypt20+13EPSS score1.95%
The mpi_powm function in Libgcrypt before 1.6.3 and GnuPG before 1.4.19 allows attackers to obtain sensitive information by leveraging timing differences when accessing a pre-computed table during modular exponentiation, related to a "Last-Level Cache Side-Channel Attack."CVE-2015-7511canonicalubuntu_linux+14EPSS score0.43%
Libgcrypt before 1.6.5 does not properly perform elliptic-point curve multiplication during decryption, which makes it easier for physically proximate attackers to extract ECDH keys by measuring electromagnetic emanations.CVE-2007-1263debiangnupg+6EPSS score5.53%
GnuPG 1.4.6 and earlier and GPGME before 1.1.4, when run from the command line, does not visually distinguish signed and unsigned portions of OpenPGP messages with multiple components, which might allow remote attackers to forge the contents of a message without detection.CVE-2016-4355canonicalubuntu_linux+3EPSS score2.15%
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.