CVE-2026-41990Disclosure(gnupg / libgcrypt)

LOWCVSS 4.0 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

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

gnupg CVEs Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-787

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

libgcrypt

Threat summary

1 mentions across 1 observed day

What's happening

Technical details provided in 1 signal
Disclosure: 1 classified signal
1 total mentions across 1 day

Affected systems

Vendors

gnupg

Products

libgcrypt

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

Disclosure

1100.0%

Referenced assets1 URL

By indicator

https://www.cve.org/CVERecord?id=CVE-2026-41990

Full discourse1 post

CVE@CVEnew168d
Disclosure
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. https://www.cve.org/CVERecord?id=CVE-2026-41990
Post summary
The advisory reports that Libgcrypt before 1.12.2 mishandles Dilithium signing with an unchecked write to a static array, though it does not use attacker-controlled data, and no PoC, exploit, or patch is discussed.
0000062
57.2K followersView on X

CPE platform detail1 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

1 of 1 entries

Part	Vendor	Product	Version	Target SW	Target HW
App	gnupg	libgcrypt	-	-	-

Explore more

Back to dashboard gnupg CVEs libgcrypt vulnerabilities