# CVE-2026-24882: Memory corruption in GnuPG > A stack-based buffer overflow in GnuPG's tpm2daemon allows attackers to execute arbitrary code when handling TPM-backed keys. - **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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:** 27 Jan 2026 - **Updated:** 15 Jul 2026 - **Also known as:** ALSA-2026:2719, AZL-75266, AZL-76146, BELL-CVE-2026-24882, DEBIAN-CVE-2026-24882, ECHO-cc02-a477-2575, GHSA-mpc3-hqr8-w5f3, JLSEC-2026-565, OESA-2026-1300, OESA-2026-1301, OESA-2026-1302, OESA-2026-1336, RHSA-2026:2719, RHSA-2026:2753, RLSA-2026:2719, ROOT-OS-DEBIAN-12-CVE-2026-24882, ROOT-OS-DEBIAN-13-CVE-2026-24882, SUSE-SU-2026:0434-1, SUSE-SU-2026:20444-1, SUSE-SU-2026:20487-1 ## What is CVE-2026-24882? CVE-2026-24882 is a high-severity memory corruption vulnerability in GnuPG, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT command for TPM-backed RSA and ECC keys. Weakness: CWE-121 (Stack-based Buffer Overflow) ## Which versions are affected by CVE-2026-24882? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gnupg2` | AlmaLinux:10 | All versions | 2.4.5-4.el10_1 | | `gnupg2-smime` | AlmaLinux:10 | All versions | 2.4.5-4.el10_1 | | `gnupg2` | Red Hat:enterprise_linux:10.1 | All versions | 0:2.4.5-4.el10_1 | | `gnupg2-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:2.4.5-4.el10_1 | | `gnupg2-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:2.4.5-4.el10_1 | | `gnupg2-smime` | Red Hat:enterprise_linux:10.1 | All versions | 0:2.4.5-4.el10_1 | | `gnupg2-smime-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:2.4.5-4.el10_1 | | `gnupg2` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:2.4.5-2.el10_0.2 | | `gnupg2-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:2.4.5-2.el10_0.2 | | `gnupg2-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:2.4.5-2.el10_0.2 | | `gnupg2-smime` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:2.4.5-2.el10_0.2 | | `gnupg2-smime-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:2.4.5-2.el10_0.2 | | `gnupg2` | Rocky Linux:10 | All versions | 0:2.4.5-4.el10_1 | | `gpg2` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.4.4-150600.3.15.1 | | `gpg2` | SUSE:Linux Enterprise Server 15 SP6-LTSS | All versions | 2.4.4-150600.3.15.1 | | `gpg2` | SUSE:Linux Enterprise Server for SAP Applications 15 SP6 | All versions | 2.4.4-150600.3.15.1 | | `gpg2` | SUSE:Linux Micro 6.0 | All versions | 2.4.4-7.1 | | `gpg2` | SUSE:Linux Micro 6.1 | All versions | 2.4.4-slfo.1.1_7.1 | | `gpg2` | openSUSE:Leap 15.6 | All versions | 2.4.4-150600.3.15.1 | Products: Gnupg Gnupg, Gpg4win Gpg4win. ## How do I fix CVE-2026-24882? Upgrade to a fixed version. ## Is CVE-2026-24882 being exploited? There is no known exploitation of CVE-2026-24882 in the wild and no public exploit code. ## Other vulnerabilities in GnuPG - [CVE-2022-3515](https://insights.sbomify.com/CVE-2022-3515/): Integer overflow in libksba (critical 9.8) - [CVE-2008-1530](https://insights.sbomify.com/CVE-2008-1530/): Memory corruption in n/a (critical 9.3) - [CVE-2026-24881](https://insights.sbomify.com/CVE-2026-24881/): Memory corruption in GnuPG (high 8.1) - [CVE-2025-68973](https://insights.sbomify.com/CVE-2025-68973/): Memory corruption in GnuPG (high 7.8) - [CVE-2020-25125](https://insights.sbomify.com/CVE-2020-25125/): Memory corruption in n/a (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-24882 and fix it if it is affected. What it is: CVE-2026-24882 is a high-severity memory corruption vulnerability in GnuPG, published on 27 Jan 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-24882 in the wild and no public exploit code. Affected product: GnuPG. 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-24882/ (Markdown: https://insights.sbomify.com/CVE-2026-24882/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24882 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24882 - OSV: https://osv.dev/vulnerability/CVE-2026-24882 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-24882/ Summaries are generated and may contain mistakes; the official description above is the record.