CVE-2025-68973: In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intend

Q: How do I fix CVE-2025-68973?

gnupg: upgrade to newer than 2.4.8. Exact commands for each OS are on this page.

Q: Is CVE-2025-68973 being exploited?

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

Q: What does CVE-2025-68973 affect?

CVE-2025-68973 affects gnupg. Severity is high (CVSS 7.8). 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.)

Routine

HIGH 7.8UPGRADE

CVE-2025-68973 is a high-severity flaw (CVSS 7.8) affecting gnupg. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 96%)
CISA exploited list	No
Weakness	CWE-675, CWE-787
Published	2025-12-28
Last modified	2026-10-13

Publisher (CNA): MITRE · Vendor: gnupg

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

Am I affected?

Timeline

2025-12-28 17:16 UTCPublished CVE record published
2026-10-13 09:10 UTCUpdated Record last modified

gnupg gnupg UPGRADE

Affected: <= 2.4.8

Fixed in: newer than 2.4.8

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 2.4.8 (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.

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-2025-68973?

gnupg: upgrade to newer than 2.4.8. Exact commands for each OS are on this page.

Is CVE-2025-68973 being exploited?

CVE-2025-68973 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-2025-68973 affect?

CVE-2025-68973 affects gnupg. Severity is high (CVSS 7.8). 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.)

How urgent is CVE-2025-68973?

Priority 28/100. High severity

Software pages

GnuPG vulnerabilities

Related CVEs

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-2026-24883 LOW 3.7 UPGRADE UPGRADE In GnuPG before 2.5.17, a long signature packet length causes parse_signature to return success with sig->data
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