# CVE-2026-41989: Memory corruption in Libgcrypt > A heap-based buffer overflow in Libgcrypt allows attackers to cause denial of service via crafted ECDH ciphertext. - **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Apr 2026 - **Updated:** 15 Oct 2026 - **Also known as:** ALSA-2026:47117, ALSA-2026:50144, ALSA-2026:50147, AZL-83544, BELL-CVE-2026-41989, CLSA-2026-1784632339, CLSA-2026-1784633299, DEBIAN-CVE-2026-41989, ECHO-afba-f32f-e1d7, GHSA-wrv8-79m2-qg24, JLSEC-2026-496, MGASA-2026-0212, OESA-2026-2345, OESA-2026-2346, OESA-2026-2347, OESA-2026-2348, 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, RLSA-2026:47117, RLSA-2026:50144, RLSA-2026:50147, ROOT-OS-DEBIAN-12-CVE-2026-41989, SUSE-SU-2026:22760-1, SUSE-SU-2026:22826-1, SUSE-SU-2026:22907-1, SUSE-SU-2026:22919-1, SUSE-SU-2026:3182-1, SUSE-SU-2026:3491-1, SUSE-SU-2026:3921-1, UBUNTU-CVE-2026-41989, openSUSE-SU-2026:21387-1 ## What is CVE-2026-41989? CVE-2026-41989 is a medium-severity memory corruption vulnerability in gnupg Libgcrypt, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2026-41989? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libgcrypt` | AlmaLinux:10 | All versions | 1.11.0-7.el10_2 | | `libgcrypt-devel` | AlmaLinux:10 | All versions | 1.11.0-7.el10_2 | | `libgcrypt` | AlmaLinux:8 | All versions | 1.8.5-8.el8_10 | | `libgcrypt-devel` | AlmaLinux:8 | All versions | 1.8.5-8.el8_10 | | `libgcrypt` | AlmaLinux:9 | All versions | 1.10.0-13.el9_8 | | `libgcrypt-devel` | AlmaLinux:9 | All versions | 1.10.0-13.el9_8 | | `libgcrypt` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.11.0-7.el10_2 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.11.0-7.el10_2 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.11.0-7.el10_2 | | `libgcrypt-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.11.0-7.el10_2 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.11.0-7.el10_2 | | `libgcrypt` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-8.el8_10 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-8.el8_10 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-8.el8_10 | | `libgcrypt-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-8.el8_10 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.8.5-8.el8_10 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt-devel-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:1.11.0-5.el10_0.1 | | `libgcrypt` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.8.5-4.el8_4.1 | | `libgcrypt` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.8.5-7.el8_6.1 | | `libgcrypt` | Red Hat:rhel_e4s:8.8::baseos | All versions | 0:1.8.5-7.el8_8.1 | | `libgcrypt` | Red Hat:rhel_e4s:9.2::baseos | All versions | 0:1.10.0-10.el9_2.2 | | `libgcrypt` | Red Hat:rhel_e4s:9.4::baseos | All versions | 0:1.10.0-10.el9_4.2 | | `libgcrypt` | Red Hat:rhel_eus:9.6::baseos | All versions | 0:1.10.0-11.el9_6.1 | | `libgcrypt` | Red Hat:rhel_eus_long_life:8.4::baseos | All versions | 0:1.8.5-4.el8_4.1 | | `libgcrypt` | Red Hat:rhel_eus_long_life:8.6::baseos | All versions | 0:1.8.5-7.el8_6.1 | | `libgcrypt` | Red Hat:rhel_tus:8.8::baseos | All versions | 0:1.8.5-7.el8_8.1 | | `libgcrypt` | Rocky Linux:10 | All versions | 0:1.11.0-7.el10_2 | | `libgcrypt` | Rocky Linux:8 | All versions | 0:1.8.5-8.el8_10 | | `libgcrypt` | Rocky Linux:9 | All versions | 0:1.10.0-13.el9_8 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.9.4-150400.6.14.1 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.9.4-150400.6.14.1 | | `libgcrypt` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.9.4-150500.12.6.1 | Products: Gnupg Libgcrypt. ## How do I fix CVE-2026-41989? Upgrade to a fixed version. ## Is CVE-2026-41989 being exploited? There is no known exploitation of CVE-2026-41989 in the wild and no public exploit code. ## Other vulnerabilities in gnupg Libgcrypt - [CVE-2021-3345](https://insights.sbomify.com/CVE-2021-3345/): Memory corruption in n/a (high 7.8) - [CVE-2018-6829](https://insights.sbomify.com/CVE-2018-6829/): Weak cryptography in n/a (high 7.5) - [CVE-2021-40528](https://insights.sbomify.com/CVE-2021-40528/): Weak cryptography in n/a (medium 5.9) - [CVE-2019-12904](https://insights.sbomify.com/CVE-2019-12904/): Information disclosure in n/a (medium 5.9) - [CVE-2017-9526](https://insights.sbomify.com/CVE-2017-9526/): Information disclosure in n/a (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-41989 and fix it if it is affected. What it is: CVE-2026-41989 is a medium-severity memory corruption vulnerability in gnupg Libgcrypt, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-41989 in the wild and no public exploit code. Affected product: gnupg Libgcrypt. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-41989/ (Markdown: https://insights.sbomify.com/CVE-2026-41989/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41989 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41989 - OSV: https://osv.dev/vulnerability/CVE-2026-41989 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-41989/ Summaries are generated and may contain mistakes; the official description above is the record.