CVE-2026-24882
Gnupg buffer overflow
- Published27 Jan 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:2719
- https://access.redhat.com/errata/RHSA-2026:2753
- https://access.redhat.com/security/cve/CVE-2026-24882
- https://bugzilla.redhat.com/show_bug.cgi?id=2433464
- https://dev.gnupg.org/T8045
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-24882.json
- https://www.openwall.com/lists/oss-security/2026/01/27/8
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-24882 being actively exploited?
CVE-2026-24882 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.44%.
How severe is CVE-2026-24882?
CVE-2026-24882 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.44% probability of exploitation.
Which products are affected by CVE-2026-24882?
Affected products include Gnupg, Gpg4win.
How do I fix CVE-2026-24882?
Upgrade affected software to a fixed version, for example Gnupg 2.5.17, Gpg4win 5.0.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-24882 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.