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.

Published: 2026-04-23 Last update: 2026-04-27 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-41990 is rated Low Risk (16.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-41990

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41990

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.0 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.4 2.5 [email protected]

Weakness enumeration for CVE-2026-41990

GitHub Security Advisory for CVE-2026-41990

GHSA-78pv-qq8x-94px · Severity: medium — Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds...

OS Trackers for CVE-2026-41990

vendor priority summary link
debian unimportant CVE-2026-41990 unimportant priority: Debian including 1 source packages (libgcrypt20), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-41990
suse low — https://www.suse.com/security/cve/CVE-2026-41990/
ubuntu medium CVE-2026-41990 medium priority: Ubuntu including 1 source packages (libgcrypt20), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, resolute, upstream, xenial): not-affected 6, needed 1, released 1. https://ubuntu.com/security/CVE-2026-41990

Affected software / configurations for CVE-2026-41990

Vendor Product Version Raw CPE
gnupg libgcrypt >= 1.12.0, < 1.12.2 cpe:2.3:a:gnupg:libgcrypt:*:*:*:*:*:*:*:*

References for CVE-2026-41990

cvelogic Threat Intelligence