CVE-2026-41990 Details
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.
A vulnerability exists in Libgcrypt versions prior to 1.12.2, specifically within the Dilithium signing algorithm. The issue arises from a static array being written to without proper bounds checking, although it does not involve attacker-controlled data. This vulnerability has been reported to have a low real-world severity, as the context in question is defined by the protocol or implementation and not influenced by external factors.
Users can upgrade to Libgcrypt version 1.12.2, which includes the necessary bounds check in the Dilithium context handling. This version is fully compatible with earlier releases. Instructions for downloading Libgcrypt 1.12.2 are available on the GnuPG website.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 23, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://dev.gnupg.org/T8208 | [email protected] | Broken Link |
| https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000503.html | [email protected] | Mailing ListRelease Notes |
| https://www.openwall.com/lists/oss-security/2026/04/21/1 | [email protected] | Mailing ListRelease Notes |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| gnupg libgcrypt | >= 1.12.0, < 1.12.2 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 27, 2026 | Initial Analysis | [email protected] |
| Apr 23, 2026 | New CVE Received | [email protected] |