CVE-2026-41990 json
Libgcrypt before 1.12.2 mishandles Dilithium signing
published 6mo ago modified 14d ago also EUVD-2026-25193 , GHSA-78pv-qq8x-94px , JLSEC-2026-497
- cvss
- 4.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
Libgcrypt before 1.12.2 mishandles Dilithium signing. Writes to a static array lack a bounds check but do not use attacker-controlled data.
Patch / fix
- julia Libgcrypt_jll 1.12.2+0
- gnupg Libgcrypt 1.12.2
- libgcrypt20 Debian 14 1.12.2-1
debian advisories DEBIAN-CVE-2026-41990
- libgcrypt20 Ubuntu 26.04 LTS 1.12.0-2ubuntu0.1
- libgcrypt20 Ubuntu Pro FIPS-updates 24.04 LTS 1.12.0-2ubuntu0.1~Fips1~rc11
ubuntu advisories UBUNTU-CVE-2026-41990
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- libgcrypt hummingbird 1 1.12.2-1.hum1
red hat advisories RHSA-2026:8466
- libgcrypt SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 1.12.1-160000.2.1
suse advisories SUSE-SU-2026:22270-1SUSE-SU-2026:22355-1
- libgcrypt openSUSE Leap 16.0 1.12.1-160000.2.1
opensuse advisories openSUSE-SU-2026:21047-1
Is CVE-2026-41990 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-41990 updated cvss 3.3
Libgcrypt: Libgcrypt: Denial of Service or data integrity issues from missing bounds check during Dilithium signing.
-
Red Hat Enterprise Linux 6 libgcrypt Red Hat Enterprise Linux 7 libgcrypt Red Hat Enterprise Linux 8 libgcrypt, thunderbird Red Hat Enterprise Linux 9 libgcrypt, thunderbird Red Hat Enterprise Linux 10 libgcrypt, thunderbird Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-core-bff-rhel9, rhoai/odh-dashboard-rhel9, rhoai/odh-mod-arch-maas-rhel9, rhoai/odh-mod-arch-automl-rhel9, rhoai/odh-mod-arch-gen-ai-rhel9, rhoai/odh-mod-arch-mlflow-rhel9, +6 moreunder investigation
-
Red Hat Hardened Images libgcrypt 1.12.2-1.hum1fixed: vendor fix RHSA-2026:8466
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-kube-rbac-proxy-rhel9, rhoai/odh-maas-controller-rhel9, rhoai/odh-mlflow-operator-rhel9, rhoai/odh-model-controller-rhel9, rhoai/odh-ogx-k8s-operator-rhel9, +14 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.0 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L |
| OSV | 3.1 | 4.0 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| julia | Libgcrypt_jll | >=1.12.0+0, <1.12.2+0 |
1.12.2+0 |
Affected products
- gnupg Libgcrypt
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
lists.gnupg.org
/pipermail/gnupg-announce/2026q2/000503.html
mailing-list, release-notes, web
-
openwall.com
/lists/oss-security/2026/04/21/1
mailing-list, release-notes, web
-
dev.gnupg.org
/T8208
broken-link, web
-
github.com
/advisories/GHSA-78pv-qq8x-94px
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-41990
web
Sources
- CVE List CVE-2026-41990
- NVD CVE-2026-41990
- OSV JLSEC-2026-497
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.