Skip to main content
CVE-2026-57062VulnerabilityPublished Updated

SUSE · Security update for gpg2

Affects SUSESource GCVE Database

0
Compare

Not known to be exploited.

Data as of 31 Oct 2026, 20:20 UTC

Severity
Low

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

EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

AI-suggested

A security update for gpg2 has been issued by the SUSE Product Security Team addressing this vulnerability. Users should apply the update to the affected gpg2 packages as provided by their SUSE distribution. Patch status is not explicitly confirmed in the data; therefore, users should consult the official SUSE advisories for current remediation guidance.

Description

A security update for gpg2 addresses a low severity vulnerability (CVE-2026-57062) involving improper handling of the CMS format for AES-GCM in the gpgsm component, which could cause parsing errors. No specific affected versions or patch details are provided in the available data.

References

Community reviews

Loading reviews…