Gnupg

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).

Published: 2026-01-27T18:43:18.883Z
Updated: 2026-01-28T15:52:11.076Z

In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT command for TPM-backed RSA and ECC keys.

Published: 2026-01-27T18:40:18.166Z
Updated: 2026-06-30T12:06:35.713Z

In GnuPG before 2.5.17, a crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped session key can cause a stack-based buffer overflow in gpg-agent during PKDECRYPT--kem=CMS handling. This can easily be leveraged for denial of service; however, there is also memory corruption that could lead to remote code execution.

Published: 2026-01-27T18:36:56.727Z
Updated: 2026-06-30T12:06:35.993Z

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.)

Published: 2025-12-28T16:19:11.019Z
Updated: 2026-04-30T03:55:53.604Z

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.

Published: 2025-12-27T22:52:30.957Z
Updated: 2026-01-02T20:44:27.393Z