CVE-2026-24882VulnerabilityPublished 29 Jan 2026Updated 12 Oct 2026

SUSE · Security update for gpg2

Affects SUSESource GCVE Database

Mentioned vulnerabilities

CVE-2026-24883

Not known to be exploited : upgrade to 11 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SUSE to 11.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=10 <11 =10.0	Fixed in 11

AI-suggested

A security update is available from Red Hat and should be applied promptly. The update fixes the identified vulnerabilities in gpg2 for Red Hat Enterprise Linux 10 and related variants. Refer to the Red Hat advisory RHSA-2026:2719 and the update instructions at https://access.redhat.com/articles/11258 for detailed remediation steps. No additional mitigations are specified beyond applying the official update.

Description

This security update for gpg2 addresses multiple vulnerabilities including a stack-based buffer overflow in TPM2 PKDECRYPT for TPM-backed RSA and ECC keys (CVE-2026-24882), a denial of service caused by long signature packet length (CVE-2026-24883), and acceptance of path separators and path traversals in the literal data filename field. These vulnerabilities could allow arbitrary code execution or denial of service. The update is rated as important by Red Hat and fixes these issues in Red Hat Enterprise Linux 10 and related variants. A security update is available and should be applied.

Impact

Successful exploitation of the stack-based buffer overflow (CVE-2026-24882) could allow an attacker to execute arbitrary code with the privileges of the gpg2 process. The denial of service vulnerability (CVE-2026-24883) could cause gpg2 to crash or become unresponsive when processing specially crafted signature packets. The acceptance of path separators and path traversal in the literal data filename field could lead to unintended file system access or manipulation. These issues collectively pose a high security risk to systems running affected versions of gpg2.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Oct 2026, 22:45 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats