Approved changes feed: RSS · Atom
cpe:2.3:a:suse:fleet:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Suse (ec535637-432e-5a38-96dd-4ec1e0138f73) |
|---|---|
| Product | Fleet (5e9e826e-c769-5388-9039-a3a0bc5ddded) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-23390 |
vulnerable | 2026-11-03 10:03:01.957644 |
Fleet doesn’t validate a server’s certificate when connecting through SSH
MEDIUM (6.3)
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.
Published: 2026-10-15T08:16:46.096Z
Updated: 2026-10-15T14:21:33.655Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.