CVE-2026-41990: Libgcrypt before 1.12.2 mishandles Dilithium signing

Routine

MEDIUM 4.0UPGRADE

CVE-2026-41990 is a medium-severity flaw (CVSS 4.0) affecting libgcrypt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.0 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 86%)
CISA exploited list	No
Weakness	CWE-787
Published	2026-04-23
Last modified	2026-10-26

Publisher (CNA): MITRE · Vendor: gnupg

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

Am I affected?

Timeline

2026-04-23 05:16 UTCPublished CVE record published
2026-10-26 21:10 UTCUpdated Record last modified

gnupg libgcrypt UPGRADE

Affected: >= 1.12.0 and < 1.12.2

Fixed in: 1.12.2

Safe to downgrade to: a release before 1.12.0

1. Check installed version

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

2. UPGRADE to 1.12.2 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libgcrypt

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 1.12.0 (Debian / Ubuntu)

apt-cache madison libgcrypt sudo apt install libgcrypt=<VERSION_BEFORE_1.12.0> sudo apt-mark hold libgcrypt

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

dnf --showduplicates list libgcrypt sudo dnf downgrade libgcrypt-<VERSION_BEFORE_1.12.0> sudo dnf versionlock add libgcrypt

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-41990?

libgcrypt: upgrade to 1.12.2. Exact commands for each OS are on this page.

Is CVE-2026-41990 being exploited?

CVE-2026-41990 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-41990 affect?

CVE-2026-41990 affects libgcrypt. Severity is medium (CVSS 4.0). Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data.

How urgent is CVE-2026-41990?

Priority 17/100. No elevated risk signals yet.

Software pages

GnuPG vulnerabilities

Related CVEs

CVE-2026-41989 MEDIUM 6.7 UPGRADE Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH c

References

← Back to latest CVEs