Security readout for executives and security teams
Plain-English summary
GnuPG before 2.5.17 has a high-impact memory safety flaw in tpm2daemon. The issue is tied to decryption operations using TPM-backed RSA or ECC keys. A successful local attack could compromise confidentiality, integrity, and availability on affected systems.
Executive priority
Treat as high priority for systems using GnuPG TPM-backed keys. Patch promptly, especially on shared workstations, servers with local user access, or environments where key confidentiality is business-critical.
Technical view
CVE-2026-24882 is a CWE-121 stack-based buffer overflow in GnuPG tpm2daemon while handling the PKDECRYPT command for TPM-backed RSA and ECC keys. CVSS 3.1 is 8.4 with local attack vector, low complexity, no privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is most likely where GnuPG before 2.5.17 is installed and TPM-backed RSA or ECC keys are used through tpm2daemon. The source bundle does not identify other affected products or remote exposure.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not state active exploitation. The CVSS vector indicates local exploitation with no privileges or user interaction required, but the bundle does not provide exploit maturity details.
Researcher notes
The strongest details are the CVE description, CVSS vector, CWE, and fixed-before version boundary. The bundle does not include proof-of-concept details, exploit status, or deeper root-cause analysis beyond PKDECRYPT handling in tpm2daemon.
Mitigation direction
Upgrade GnuPG to version 2.5.17 or later.
Apply relevant vendor updates, including listed Red Hat advisories where applicable.
Prioritize systems using TPM-backed RSA or ECC keys.
Check vendor guidance if package status differs by distribution.
Validation and detection
Inventory installed GnuPG versions across endpoints and servers.
Identify hosts using tpm2daemon with TPM-backed RSA or ECC keys.
Confirm vendor packages include the CVE fix.
Review local-user access on affected hosts until updated.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.