Fleet doesn’t validate a server’s certificate when connecting through SSH
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SUSE | fleet | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Suse | Fleet |
|
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-12541 | Fleet doesn’t validate a server’s certificate when connecting through SSH |
Github GHSA |
GHSA-xgpc-q899-67p8 | Fleet doesn’t validate a server’s certificate when connecting through SSH |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.190% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Suse
Suse fleet |
|
| Vendors & Products |
Suse
Suse fleet |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Fleet doesn’t validate a server’s certificate when connecting through SSH | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV3_1
|