Name
gnupg
Version
2.3.7
Type
library
Description
GNU Privacy Guard - encryption and signing tools (2.x)
Licenses
GPL-3.0-only & LGPL-3.0-only
PURL
-
CPE
cpe:2.3:*:gnupg:gnupg:2.3.7:*:*:*:*:*:*:*
Other Versions#
Patches#
#
Title
Author
Resolve
1
use pkgconfig instead of npth config
Saul Wold <sgw@linux.intel.com>
2
gpg: Fix a verification DoS due to a malicious subkey in the
Yogita Urade <yogita.urade@windriver.com>
CVE-2025-30258
3
Woverride-init is not needed with gcc 9
Khem Raj <raj.khem@gmail.com>
4
gpg: Fix double free of internal data.
Werner Koch <wk@gnupg.org>
CVE-2025-30258
5
Allow the environment to override where gnupg looks for its
Ross Burton <ross.burton@intel.com>
6
gpg: Remove a signature check function wrapper.
Werner Koch <wk@gnupg.org>
CVE-2025-30258
7
configure.ac: use a custom value for the location of
Alexander Kanavin <alex.kanavin@gmail.com>
8
gpg: Fix regression for the recent malicious subkey DoS fix.
Werner Koch <wk@gnupg.org>
CVE-2025-30258
9
gpg: Fix possible memory corruption in the armor parser.
Werner Koch <wk@gnupg.org>
CVE-2025-68973
10
autogen.sh: fix find-version for beta checking
Wenzong Fan <wenzong.fan@windriver.com>
11
gpg: Lookup key for merging/inserting only by primary key.
Werner Koch <wk@gnupg.org>
CVE-2025-30258
Vulnerabilities#
Name
Analysis
Description
Patched
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Exploitable
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.
Patched
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."