Skip to main content

Libgcrypt EUVDEUVD-2026-25193

| CVE-2026-41990 MEDIUM
Out-of-bounds Write (CWE-787)
2026-04-23 mitre GHSA-78pv-qq8x-94px
4.0
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
4.0 MEDIUM
AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
SUSE
3.6 LOW
AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Red Hat
3.3 LOW
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Attack Vector
Local
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Lifecycle Timeline

6
Patch released
Apr 27, 2026 - 18:33 nvd
Patch available
Analysis Generated
Apr 23, 2026 - 07:08 vuln.today
Patch available
Apr 23, 2026 - 06:16 EUVD
EUVD ID Assigned
Apr 23, 2026 - 05:00 euvd
EUVD-2026-25193
Analysis Generated
Apr 23, 2026 - 05:00 vuln.today
CVE Published
Apr 23, 2026 - 04:39 nvd
MEDIUM 4.0

DescriptionCVE.org

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

AnalysisAI

Libgcrypt before version 1.12.2 contains a bounds-check vulnerability in Dilithium signing operations where writes to a static array lack proper bounds validation, potentially causing memory corruption and integrity loss. The vulnerability affects local attackers with non-privileged access on systems running vulnerable versions 1.12.0 and 1.12.1. While the vulnerability does not involve attacker-controlled data in the array writes themselves, the missing bounds check creates an integrity and availability risk through uncontrolled memory modification.

Technical ContextAI

Libgcrypt is the cryptographic library underlying GnuPG and other applications requiring cryptographic primitives. This vulnerability resides in the Dilithium signature algorithm implementation (NIST FIPS 204 post-quantum cryptography standard). The root cause is classified as CWE-787 (Out-of-bounds Write) - specifically, a static array used during Dilithium signing receives writes without validating that indices remain within allocated bounds. Although the vulnerability description notes that attacker-controlled data is not directly used in the array indexing, the lack of bounds enforcement means that legitimate code paths with certain input parameters can write beyond the array's boundaries, corrupting adjacent memory.

RemediationAI

Vendor-released patch: Libgcrypt 1.12.2 or later. Update the Libgcrypt library package immediately through your distribution's package manager (apt, yum, pacman, etc.) or download directly from https://dev.gnupg.org/. Rebuilding dependent applications (GnuPG, OpenSSL, or custom applications linked against Libgcrypt) may be necessary after the library upgrade. If immediate patching is not possible, restrict local system access to untrusted users and monitor for memory corruption errors in application logs; however, this does not eliminate the underlying risk and should be treated as temporary only. Verify successful patching by confirming Libgcrypt version with libgcrypt-config --version returns 1.12.2 or higher.

Vendor StatusVendor

SUSE

Severity: Low
Product Status
SLES15-SP5-CHOST-BYOS-SAP-CCloud Fixed
SLES15-SP6-CHOST-BYOS Fixed
SLES15-SP6-CHOST-BYOS-Aliyun Fixed
SLES15-SP6-CHOST-BYOS-Azure Fixed
SLES15-SP6-CHOST-BYOS-EC2 Fixed

Share

EUVD-2026-25193 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy