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

CVE-2026-41990 is fixed in 3 products on 1 platform, first by libgcrypt-bin 1.12.0-2ubuntu0.1, released April 22, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-41990
- Priority: Routine
- CVSS: 4.0 (medium)
- EPSS: 0.0023
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Apr 22, 2026

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

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | libgcrypt opensuse-leap 16.0 | 1.12.1-160000.2.1 | [OPENSUSE-SU-2026:21047-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21047-1.md) | Jun 24, 2026 |
| Linux | libgcrypt sles 16.0 | 1.12.1-160000.2.1 | [SUSE-SU-2026:22355-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-22355-1.md) | Jun 24, 2026 |
| Linux | libgcrypt-bin Ubuntu 26.04.1 LTS (resolute) | 1.12.0-2ubuntu0.1 | [libgcrypt-bin 1.12.0-2ubuntu0.1](https://patchblox.com/security/data/fix/linux/ubuntu-resolute-libgcrypt-bin-1.12.0-2ubuntu0.1.md) | Apr 22, 2026 |
| Linux | libgcrypt20 Debian 14 | 1.12.2-1 | [DEBIAN-CVE-2026-41990](https://patchblox.com/security/data/fix/linux/debian-cve-2026-41990.md) | May 15, 2026 |
| Linux | libgcrypt20 Ubuntu 26.04.1 LTS (resolute) | 1.12.0-2ubuntu0.1 | [libgcrypt20 1.12.0-2ubuntu0.1](https://patchblox.com/security/data/fix/linux/ubuntu-resolute-libgcrypt20-1.12.0-2ubuntu0.1.md) | Apr 22, 2026 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.