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

Source: https://junglewise.ai/threats/cve-2026-41990-libgcrypt-before-1-12-2-mishandles-dilithium-signing-writes-to-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-23  
License: CC BY 4.0 with a link back

CVE-2026-41990 · Severity: medium · CVSS 4 · Published 2026-04-23

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

Vendors: [GnuPG](https://junglewise.ai/threats/vendors/gnupg).

## Quick answers

**Is CVE-2026-41990 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-41990 being exploited in the wild.

**How severe is CVE-2026-41990?** Medium severity, with a CVSS score of 4, published 23 April 2026.

**Which products and versions are affected?** GnuPG Libgcrypt. The advisory does not name versions.

**Is there a fix for CVE-2026-41990?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-41990?** Check whether you run GnuPG Libgcrypt. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- GnuPG Libgcrypt

## Related threats

- [GnuPG Libgcrypt heap buffer overflow in ECDH decryption](https://junglewise.ai/threats/cve-2026-41989-gnupg-libgcrypt-heap-buffer-overflow-in-ecdh-decryption)