Fleet doesn’t validate a server’s certificate when connecting through SSH
A vulnerability has been identified within Fleet where, by default, Fleet will automatically trust a remote server’s certificate when connecting through SSH if the certificate isn’t set in the `known_hosts` file. This could allow the execution of a man-in-the-middle (MitM) attack against Fleet. In case the server that is being connected to has a trusted entry in the known_hosts file, then Fleet will correctly check the authenticity of the presented certificate.
CVE-2025-23390
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2025-23390
fleet
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "SUSE",
"product": "fleet",
"versions": [
{
"status": "affected",
"version": "0.9.0-rc.1",
"lessThan": "0.10.12",
"versionType": "semver"
},
{
"status": "affected",
"version": "0.11.0",
"lessThan": "0.11.7",
"versionType": "semver"
},
{
"status": "affected",
"version": "0.12.0",
"lessThan": "0.12.2",
"versionType": "semver"
}
],
"packageName": "github.com/rancher/fleet",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2025-23390
Source reference:
/cveMetadata/cveId
Publisher severity
medium
Source reference: /containers/cna/metrics
- Event
- #28778 · Revision 1
- Added to Heist Feed
- Publisher date