CVE-2025-62877: SUSE harvester · Insecure Default
Affects SUSE harvesterSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SUSEharvester | Affected
| Fixed in– |
GitHubharvester/harvesterpkg:github/harvester/harvesterOther threats | Affected
| Fixed in– |
GitHubgithub.com/harvester/harvester-installerpkg:github/github.com/harvester/harvester-installerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-62877, European organizations should immediately avoid using the interactive installer for creating new clusters or adding hosts in SUSE Harvester versions 1.5.0 and 1.6.0. Instead, they should deploy clusters using the PXE boot mechanism combined with the Harvester configuration setup, which is not affected by this vulnerability. Organizations should monitor SUSE’s official channels for patches or updated versions that address this issue and plan prompt upgrades once available. Additionally, network-level controls such as restricting SSH access to trusted management networks, implementing strict firewall rules, and employing intrusion detection systems can reduce exposure. It is also advisable to audit existing deployments for the presence of default SSH credentials and enforce immediate password changes or key-based authentication. Regular vulnerability scanning and penetration testing focused on SSH access can help detect exploitation attempts. Finally, organizations should update incident response plans to include this vulnerability and educate administrators on secure deployment practices for SUSE Harvester.
Description
Projects using the SUSE Virtualization (Harvester) environment may expose the OS default ssh login password if they are using the 1.5.x or 1.6.x interactive installer to either create a new cluster or add new hosts to an existing cluster. The environment is not affected if the PXE boot mechanism is utilized along with the Harvester configuration setup.