CVE-2026-41990 Memory corruption in Libgcrypt
Libgcrypt mishandles Dilithium signing with unchecked static array writes, potentially causing crashes or memory corruption.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41990?
CVE-2026-41990 is a medium-severity memory corruption vulnerability in gnupg Libgcrypt, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data.
Weakness: CWE-787
Which versions are affected by CVE-2026-41990?
It affects 1 product.
Linux distribution packages (4)
libgcrypt SUSE:Linux Enterprise Server 16.0 | All versions | 1.12.1-160000.2.1 |
libgcrypt SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.12.1-160000.2.1 |
libgcrypt SUSE:Linux Micro 6.2 | All versions | 1.12.1-160000.2.1 |
libgcrypt openSUSE:Leap 16.0 | All versions | 1.12.1-160000.2.1 |
Products include Gnupg Libgcrypt.
How do I fix CVE-2026-41990?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-41990 being exploited?
There is no known exploitation of CVE-2026-41990 in the wild and no public exploit code.
Other vulnerabilities in gnupg Libgcrypt
Sources
Also known as BELL-CVE-2026-41990, DEBIAN-CVE-2026-41990, GHSA-78pv-qq8x-94px, JLSEC-2026-497, SUSE-SU-2026:22270-1, SUSE-SU-2026:22355-1 and 2 more.