SUSE Fleet up to 0.10.11/0.11.6/0.12.1 certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 2.16 |
Summary
A vulnerability identified as problematic has been detected in SUSE Fleet up to 0.10.11/0.11.6/0.12.1. Affected by this vulnerability is an unknown functionality. This manipulation causes certificate validation. This vulnerability is handled as CVE-2025-23390. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in SUSE Fleet up to 0.10.11/0.11.6/0.12.1. It has been declared as problematic. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a certificate validation vulnerability. The CWE definition for the vulnerability is CWE-295. The product does not validate, or incorrectly validates, a certificate. As an impact it is known to affect integrity. The summary by CVE is:
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.
The advisory is shared at bugzilla.suse.com. This vulnerability is known as CVE-2025-23390 since 01/15/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/15/2026). MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
Upgrading to version 0.10.12, 0.11.7 or 0.12.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-211104). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 0.10.0
- 0.10.1
- 0.10.2
- 0.10.3
- 0.10.4
- 0.10.5
- 0.10.6
- 0.10.7
- 0.10.8
- 0.10.9
- 0.10.10
- 0.10.11
- 0.11.0
- 0.11.1
- 0.11.2
- 0.11.3
- 0.11.4
- 0.11.5
- 0.11.6
- 0.12.0
- 0.12.1
License
Website
- Vendor: https://www.suse.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.3
CNA Vector (suse): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Fleet 0.10.12/0.11.7/0.12.2
Timeline
01/15/2025 CVE reserved10/15/2026 Advisory disclosed
10/15/2026 VulDB entry created
10/15/2026 VulDB entry last update
Sources
Vendor: suse.comAdvisory: bugzilla.suse.com
Status: Confirmed
CVE: CVE-2025-23390 (🔒)
GCVE (CVE): GCVE-0-2025-23390
GCVE (VulDB): GCVE-100-420541
EUVD: 🔒
Entry
Created: 10/15/2026 10:47Updated: 10/15/2026 17:22
Changes: 10/15/2026 10:47 (64), 10/15/2026 17:22 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.