CVE-2026-41989: Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt.
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: gnupg Libgcrypt 1.10.4, 1.11.3, 1.12.2; azl3 libgcrypt 1.10.3-1 on Azure Linux 3.0 1.10.3-2; azl3 libgcrypt 1.10.3-2 on Azure Linux 3.0 1.10.3-2.
Low priority for now. Upgrade to gnupg Libgcrypt 1.10.4, 1.11.3, 1.12.2; azl3 libgcrypt 1.10.3-1 on Azure Linux 3.0 1.10.3-2; azl3 libgcrypt 1.10.3-2 on Azure Linux 3.0 1.10.3-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- BDU:2026-07879
- ALSA-2026:47117
- ALSA-2026:50144
- ALSA-2026:50147
- openSUSE-SU-2026:21387-1
- RHSA-2026:47117
- RHSA-2026:50144
- RHSA-2026:50147
- RHSA-2026:52950
- RHSA-2026:52951
- RHSA-2026:52952
- RHSA-2026:52953
- RHSA-2026:58977
- RHSA-2026:58978
- RHSA-2026:58979
- RHSA-2026:8466
- RLSA-2026:47117
- RLSA-2026:50144
- RLSA-2026:50147
- SUSE-SU-2026:22760-1
- Published
- Apr 23, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-787
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · mitre
- 6.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnupg | libgcrypt | cpe:2.3:a:gnupg:libgcrypt |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.
gnupg Libgcrypt
- 1.8.8 and later · before 1.10.4affected · semver
- 1.11.0 and later · before 1.11.3affected · semver
- 1.12.0 and later · before 1.12.2affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnupg libgcrypt1.8.8 and later · before 1.10.4
- gnupg libgcrypt1.11.0 and later · before 1.11.3
- gnupg libgcrypt1.12.0 and later · before 1.12.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | libgcrypt | before 1.11.0-7.el10_2 | 1.11.0-7.el10_2 |
| AlmaLinux:10 | libgcrypt-devel | before 1.11.0-7.el10_2 | 1.11.0-7.el10_2 |
| AlmaLinux:8 | libgcrypt | before 1.8.5-8.el8_10 | 1.8.5-8.el8_10 |
| AlmaLinux:8 | libgcrypt-devel | before 1.8.5-8.el8_10 | 1.8.5-8.el8_10 |
| AlmaLinux:9 | libgcrypt | before 1.10.0-13.el9_8 | 1.10.0-13.el9_8 |
| AlmaLinux:9 | libgcrypt-devel | before 1.10.0-13.el9_8 | 1.10.0-13.el9_8 |
| Debian:12 | libgcrypt20 | before 1.10.1-3+deb12u1 | 1.10.1-3+deb12u1 |
| Debian:13 | libgcrypt20 | before 1.11.0-7+deb13u1 | 1.11.0-7+deb13u1 |
| Debian:14 | libgcrypt20 | before 1.12.2-1 | 1.12.2-1 |
| openSUSE:Leap 16.0 | libgcrypt | before 1.12.1-160000.3.1 | 1.12.1-160000.3.1 |
| Red Hat:enterprise_linux_eus:10.0 | libgcrypt | before 0:1.11.0-5.el10_0.1 | 0:1.11.0-5.el10_0.1 |
| Red Hat:enterprise_linux:10.2 | libgcrypt | before 0:1.11.0-7.el10_2 | 0:1.11.0-7.el10_2 |
| Red Hat:enterprise_linux:10.2 | libgcrypt-debuginfo | before 0:1.11.0-7.el10_2 | 0:1.11.0-7.el10_2 |
| Red Hat:enterprise_linux:10.2 | libgcrypt-debugsource | before 0:1.11.0-7.el10_2 | 0:1.11.0-7.el10_2 |
| Red Hat:enterprise_linux:10.2 | libgcrypt-devel | before 0:1.11.0-7.el10_2 | 0:1.11.0-7.el10_2 |
| Red Hat:enterprise_linux:10.2 | libgcrypt-devel-debuginfo | before 0:1.11.0-7.el10_2 | 0:1.11.0-7.el10_2 |
| Red Hat:enterprise_linux:8::baseos | libgcrypt | before 0:1.8.5-8.el8_10 | 0:1.8.5-8.el8_10 |
| Red Hat:enterprise_linux:8::baseos | libgcrypt-debuginfo | before 0:1.8.5-8.el8_10 | 0:1.8.5-8.el8_10 |
| Red Hat:enterprise_linux:8::baseos | libgcrypt-debugsource | before 0:1.8.5-8.el8_10 | 0:1.8.5-8.el8_10 |
| Red Hat:enterprise_linux:8::baseos | libgcrypt-devel | before 0:1.8.5-8.el8_10 | 0:1.8.5-8.el8_10 |
| Red Hat:enterprise_linux:8::baseos | libgcrypt-devel-debuginfo | before 0:1.8.5-8.el8_10 | 0:1.8.5-8.el8_10 |
| Red Hat:enterprise_linux:9::appstream | libgcrypt-debuginfo | before 0:1.10.0-13.el9_8 | 0:1.10.0-13.el9_8 |
| Red Hat:enterprise_linux:9::appstream | libgcrypt-debugsource | before 0:1.10.0-13.el9_8 | 0:1.10.0-13.el9_8 |
| Red Hat:enterprise_linux:9::appstream | libgcrypt-devel | before 0:1.10.0-13.el9_8 | 0:1.10.0-13.el9_8 |
+19
Same product
gnupg: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-33560Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel…31Monitor
- CVE-2021-3345_gcry_md_block_write in cipher/hash-common.c in Libgcrypt version 1.9.0 has a heap-based buffer overflow when the digest final function…31Monitor
- CVE-2018-6829cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-12904Jun 20, 2019 · In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are…24Monitor
- ← EarlierCVE-2021-40528Sep 6, 2021 · The ElGamal implementation in Libgcrypt before 1.9.4 allows plaintext recovery because, during interaction between two cryptographic…23Monitor
- Later →CVE-2026-41990Apr 23, 2026 · Libgcrypt before 1.12.2 mishandles Dilithium signing.16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| gnupg Libgcrypt | 1.10.4 | Vendor (CNA) |
| gnupg Libgcrypt | 1.11.3 | Vendor (CNA) |
| gnupg Libgcrypt | 1.12.2 | Vendor (CNA) |
| azl3 libgcrypt 1.10.3-1 on Azure Linux 3.0 | 1.10.3-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 libgcrypt 1.10.3-2 on Azure Linux 3.0 | 1.10.3-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libgcrypt 1.10.3-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| almalinux:libgcrypt | 1.8.5-8.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:libgcrypt-devel | 1.8.5-8.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:libgcrypt20 | 1.10.1-3+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:libgcrypt | 1.12.1-160000.3.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:libgcrypt | 0:1.8.5-8.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libgcrypt-debuginfo | 0:1.8.5-8.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libgcrypt-debugsource | 0:1.8.5-8.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libgcrypt-devel | 0:1.8.5-8.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:libgcrypt-devel-debuginfo | 0:1.8.5-8.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| rocky linux:libgcrypt | 0:1.8.5-8.el8_10 · Rocky Linux:8 | Package registry (OSV) |
| suse:libgcrypt | 1.12.1-160000.3.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-419900 days apartLibgcrypt before 1.12.2 mishandles Dilithium signing.16Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.