SUSE · Security update for gpg2
Affects SUSESource GCVE Database
Not known to be exploited.
Data as of 16 Nov 2026, 20:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 16 Nov 2026.
What to do
AI-suggested
A security update has been released by the SUSE Product Security Team to address these issues. Users should apply the official update to gpg2 to remediate the vulnerabilities. No additional mitigation steps are indicated.
Description
A security update for gpg2 addresses two issues: allowing the use of an ADSK subkey as an ADSK subkey (CVE-2025-30258) and preventing the installation of expired SKS certificates. The update fixes these vulnerabilities to improve the security of the gpg2 software.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2025/suse-su-2025_20465-1.json (opens in a new tab)
- suse.com/support/update/announcement/2025/suse-su-202520465-1/ (opens in a new tab)
- lists.suse.com/pipermail/sle-updates/2025-July/040660.html (opens in a new tab)
- bugzilla.suse.com/1236931 (opens in a new tab)
- bugzilla.suse.com/1239119 (opens in a new tab)
- bugzilla.suse.com/1243069 (opens in a new tab)
- suse.com/security/cve/CVE-2025-30258/ (opens in a new tab)