CVE-2026-24883: In GnuPG before 2.5.17, a long signature packet length causes parse_signature to return success with sig->data

Routine

LOW 3.7REMOTEUPGRADEUPGRADE

CVE-2026-24883 is a low-severity flaw (CVSS 3.7) affecting gnupg, gpg4win. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-476
Published	2026-01-27
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: gnupg · gpg4win

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-27 19:16 UTCPublished CVE record published
2026-06-17 10:23 UTCUpdated Record last modified

gnupg gnupg UPGRADE

Affected: >= 2.5.13 and < 2.5.17

Fixed in: 2.5.17

Safe to downgrade to: a release before 2.5.13

1. Check installed version

apt-cache policy gnupg || rpm -q gnupg || gnupg --version

2. UPGRADE to 2.5.17 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gnupg

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gnupg

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.5.13 (Debian / Ubuntu)

apt-cache madison gnupg sudo apt install gnupg=<VERSION_BEFORE_2.5.13> sudo apt-mark hold gnupg

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gnupg sudo dnf downgrade gnupg-<VERSION_BEFORE_2.5.13> sudo dnf versionlock add gnupg

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

gpg4win gpg4win UPGRADE

Affected: >= 5.0.0 and < 5.0.1

Fixed in: 5.0.1

Safe to downgrade to: a release before 5.0.0

1. Check installed version

apt-cache policy gpg4win || rpm -q gpg4win || gpg4win --version

2. UPGRADE to 5.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gpg4win

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gpg4win

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)

apt-cache madison gpg4win sudo apt install gpg4win=<VERSION_BEFORE_5.0.0> sudo apt-mark hold gpg4win

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gpg4win sudo dnf downgrade gpg4win-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add gpg4win

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-24883?

gnupg: upgrade to 2.5.17; gpg4win: upgrade to 5.0.1. Exact commands for each OS are on this page.

Is CVE-2026-24883 being exploited?

CVE-2026-24883 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-24883 affect?

CVE-2026-24883 affects gnupg, gpg4win. Severity is low (CVSS 3.7). 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).

How urgent is CVE-2026-24883?

Priority 28/100. Remotely exploitable, no login, no user action

Software pages

GnuPG vulnerabilities

Related CVEs

CVE-2025-68973 HIGH 7.8 UPGRADE In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intend
CVE-2025-68972 MEDIUM 5.9 UPGRADE In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct
CVE-2026-24882 HIGH 8.4 UPGRADE UPGRADE In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT co
CVE-2026-24881 HIGH 8.1 UPGRADE UPGRADE In GnuPG before 2.5.17, a crafted CMS (S/MIME) EnvelopedData message carrying an oversized wrapped session key
CVE-2025-30258 LOW 2.7 UPGRADE In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a

References

← Back to latest CVEs