Libgcrypt <=1.12.2 Dilithium signing static array bounds issue
CVE-2026-41990 Published on April 23, 2026
Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data.
Vulnerability Analysis
CVE-2026-41990 is exploitable with local system access, and does not require authorization privileges or user interaction. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality, with no impact on integrity and availability.
Weakness Type
What is a Memory Corruption Vulnerability?
The software writes data past the end, or before the beginning, of the intended buffer. Typically, this can result in corruption of data, a crash, or code execution. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent write operation then produces undefined or unexpected results.
CVE-2026-41990 has been classified to as a Memory Corruption vulnerability or weakness.
Products Associated with CVE-2026-41990
Want to know whenever a new CVE is published for Gnupg Libgcrypt? stack.watch will email you.
Affected Versions
gnupg Libgcrypt:- Version 1.12.0 and below 1.12.2 is affected.