Buffer Overflow in Libgcrypt Dilithium Signing (Pre

Publication date: 2026-04-23

Last updated on: 2026-04-27

Assigner: MITRE

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-04-23

Last Modified

2026-04-27

Generated

2026-07-06

AI Q&A

2026-04-24

EPSS Evaluated

2026-07-05

NVD

CVE-2026-41990

EUVD

EUVD-2026-25193

Affected Vendors & Products

Vendor	Product	Version / Range
gnupg	libgcrypt	From 1.12.0 (inc) to 1.12.2 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Impact Analysis

The vulnerability has a CVSS base score of 4.0, indicating a low to moderate severity. It requires local access with high attack complexity and no privileges or user interaction. While it does not compromise confidentiality, it can impact integrity and availability to some extent. Since the writes do not use attacker-controlled data, the risk of exploitation is limited.

Executive Summary

This vulnerability exists in Libgcrypt versions before 1.12.2 and involves improper handling of Dilithium signing. Specifically, the software writes to a static array without performing bounds checking. However, these writes do not involve attacker-controlled data.

Hi! I’m here to help you understand CVE-2026-41990. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70