Overview 26 matches · 0 in Waratek scope · 0 protected · 0 exploited · 0 CISA KEV · 3 public PoC · 0 EPSS ≥ 0.5
26matches
0in Waratek scope0.0%
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
3public PoC11.5%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
1
3.8%
Not applicable
25
96.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
26
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
3
11.5%
Proof of concept only
1
3.8%
Forecast only
0
0.0%
No public exploit
22
84.6%
split by
peak 6 / year
20051
Not applicable1
Medium1
not blocked1
No public exploit1
20063
Not applicable3
Medium3
not blocked3
Working exploit published2
No public exploit1
20071
Not applicable1
Medium1
not blocked1
Working exploit published1
20080
20090
20100
20110
20120
20133
Not applicable3
Medium3
not blocked3
No public exploit3
20141
Not applicable1
Medium1
not blocked1
No public exploit1
20150
20161
Not applicable1
Medium1
not blocked1
No public exploit1
20171
Not applicable1
Medium1
not blocked1
No public exploit1
20182
Not applicable2
Medium2
not blocked2
No public exploit2
20196
Not applicable6
Medium6
not blocked6
No public exploit6
20200
20211
Not applicable1
Medium1
not blocked1
No public exploit1
20221
Outside Waratek scope1
Medium1
not blocked1
No public exploit1
20230
20240
20252
Not applicable2
Medium2
not blocked2
Proof of concept only1
No public exploit1
20263
Not applicable3
Medium3
not blocked3
No public exploit3
20062008201020122014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-41990 | Medium | 2026-04-23 | Not applicable | No public exploit | Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data. |
| CVE-2026-41989 | Medium | 2026-04-23 | Not applicable | No public exploit | Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt. |
| CVE-2026-24883 | Medium | 2026-01-27 | Not applicable | No public exploit | In GnuPG before 2.5.17, a long signature packet length causes parse_signature to return success with sig->data[] set to a NULL value, leading to a denial of service (application crash). |
| CVE-2025-68972 | Medium | 2025-12-27 | Not applicable | Proof of concept only | In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line. |
| CVE-2025-30258 | Medium | 2025-03-19 | Not applicable | No public exploit | In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS." |
| CVE-2022-34903 | Medium | 2022-07-01 | Outside Waratek scope | No public exploit | 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. |
| CVE-2021-40528 | Medium | 2021-09-06 | Not applicable | No public exploit | 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-2015-0837 | Medium | 2019-11-29 | Not applicable | No public exploit | 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-2014-3591 | Medium | 2019-11-29 | Not applicable | No public exploit | Libgcrypt before 1.6.3 and GnuPG before 1.4.19 does not implement ciphertext blinding for Elgamal decryption, which allows physically proximate attackers to obtain the server's private key by determining factors using crafted ciphertext and the fluctuations in the electromagnetic field during multiplication. |
| CVE-2011-2207 | Medium | 2019-11-27 | Not applicable | No public exploit | dirmngr before 2.1.0 improperly handles certain system calls, which allows remote attackers to cause a denial of service (DOS) via a specially-crafted certificate. |
| CVE-2015-1607 | Medium | 2019-11-20 | Not applicable | No public exploit | 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-1606 | Medium | 2019-11-20 | Not applicable | No public exploit | 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-2019-12904 | Medium | 2019-06-20 | Not applicable | No public exploit | 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 |
| CVE-2017-7526 | Medium | 2018-07-26 | Not applicable | No public exploit | libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attacker can run arbitrary software on the hardware where the private RSA key is used. |
| CVE-2018-0495 | Medium | 2018-06-13 | Not applicable | No public exploit | 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-2017-9526 | Medium | 2017-06-11 | Not applicable | No public exploit | In Libgcrypt before 1.7.7, an attacker who learns the EdDSA session key (from side-channel observation during the signing process) can easily recover the long-term secret key. 1.7.7 makes a cipher/ecc-eddsa.c change to store this session key in secure memory, to ensure that constant-time point operations are used in the MPI library. |
| CVE-2016-6313 | Medium | 2016-12-13 | Not applicable | No public exploit | The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits. |
| CVE-2014-4617 | Medium | 2014-06-25 | Not applicable | No public exploit | The do_uncompress function in g10/compress.c in GnuPG 1.x before 1.4.17 and 2.x before 2.0.24 allows context-dependent attackers to cause a denial of service (infinite loop) via malformed compressed packets, as demonstrated by an a3 01 5b ff byte sequence. |
| CVE-2013-4402 | Medium | 2013-10-28 | Not applicable | No public exploit | 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-4351 | Medium | 2013-10-10 | Not applicable | No public exploit | 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-2012-6085 | Medium | 2013-01-24 | Not applicable | No public exploit | 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. |
| CVE-2007-1263 | Medium | 2007-03-06 | Not applicable | Working exploit published | 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-2006-6169 | Medium | 2006-11-29 | Not applicable | No public exploit | Heap-based buffer overflow in the ask_outfile_name function in openfile.c for GnuPG (gpg) 1.4 and 2.0, when running interactively, might allow attackers to execute arbitrary code via messages with "C-escape" expansions, which cause the make_printable_string function to return a longer string than expected while constructing a prompt. |
| CVE-2006-3746 | Medium | 2006-07-28 | Not applicable | Working exploit published | Integer overflow in parse_comment in GnuPG (gpg) 1.4.4 allows remote attackers to cause a denial of service (segmentation fault) via a crafted message. |
| CVE-2006-3082 | Medium | 2006-06-19 | Not applicable | Working exploit published | parse-packet.c in GnuPG (gpg) 1.4.3 and 1.9.20, and earlier versions, allows remote attackers to cause a denial of service (gpg crash) and possibly overwrite memory via a message packet with a large length (long user ID string), which could lead to an integer overflow, as demonstrated using the --no-armor option. |
| CVE-2005-0366 | Medium | 2005-05-02 | Not applicable | No public exploit | The integrity check feature in OpenPGP, when handling a message that was encrypted using cipher feedback (CFB) mode, allows remote attackers to recover part of the plaintext via a chosen-ciphertext attack when the first 2 bytes of a message block are known, and an oracle or other mechanism is available to determine whether an integrity check failed. |