IBM OpenBMC up to FW1060.81/FW1110.31/FW1120.01 BMC Firmware Management Interface information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.8 | $0-$5k | 0.13+ |
Summary
A vulnerability was found in IBM OpenBMC up to FW1060.81/FW1110.31/FW1120.01. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component BMC Firmware Management Interface. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2026-18857. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability classified as problematic has been found in IBM OpenBMC up to FW1060.81/FW1110.31/FW1120.01. This affects an unknown code block of the component BMC Firmware Management Interface. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
IBM OPENBMC FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81 is affected by a vulnerability in the BMC firmware management interface. The host system can cause the BMC firmware management service to crash or allow a limited amount of BMC internal memory to be read, resulting in a confidentiality and availability impact to the managed system.
The advisory is shared at ibm.com. This vulnerability is uniquely identified as CVE-2026-18857 since 08/04/2026. The exploitability is told to be easy. An attack has to be approached locally. The exploitation requires an enhanced level of successful 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 09/24/2026). MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- FW1060.0
- FW1060.1
- FW1060.2
- FW1060.3
- FW1060.4
- FW1060.5
- FW1060.6
- FW1060.7
- FW1060.8
- FW1060.9
- FW1060.10
- FW1060.11
- FW1060.12
- FW1060.13
- FW1060.14
- FW1060.15
- FW1060.16
- FW1060.17
- FW1060.18
- FW1060.19
- FW1060.20
- FW1060.21
- FW1060.22
- FW1060.23
- FW1060.24
- FW1060.25
- FW1060.26
- FW1060.27
- FW1060.28
- FW1060.29
- FW1060.30
- FW1060.31
- FW1060.32
- FW1060.33
- FW1060.34
- FW1060.35
- FW1060.36
- FW1060.37
- FW1060.38
- FW1060.39
- FW1060.40
- FW1060.41
- FW1060.42
- FW1060.43
- FW1060.44
- FW1060.45
- FW1060.46
- FW1060.47
- FW1060.48
- FW1060.49
- FW1060.50
- FW1060.51
- FW1060.52
- FW1060.53
- FW1060.54
- FW1060.55
- FW1060.56
- FW1060.57
- FW1060.58
- FW1060.59
- FW1060.60
- FW1060.61
- FW1060.62
- FW1060.63
- FW1060.64
- FW1060.65
- FW1060.66
- FW1060.67
- FW1060.68
- FW1060.69
- FW1060.70
- FW1060.71
- FW1060.72
- FW1060.73
- FW1060.74
- FW1060.75
- FW1060.76
- FW1060.77
- FW1060.78
- FW1060.79
- FW1060.80
- FW1060.81
- FW1110.0
- FW1110.1
- FW1110.2
- FW1110.3
- FW1110.4
- FW1110.5
- FW1110.6
- FW1110.7
- FW1110.8
- FW1110.9
- FW1110.10
- FW1110.11
- FW1110.12
- FW1110.13
- FW1110.14
- FW1110.15
- FW1110.16
- FW1110.17
- FW1110.18
- FW1110.19
- FW1110.20
- FW1110.21
- FW1110.22
- FW1110.23
- FW1110.24
- FW1110.25
- FW1110.26
- FW1110.27
- FW1110.28
- FW1110.29
- FW1110.30
- FW1110.31
- FW1120.01
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.8VulDB Meta Temp Score: 2.8
VulDB Base Score: 2.3
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.4
CNA Vector (ibm): 🔒
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/04/2026 CVE reserved09/24/2026 Advisory disclosed
09/24/2026 VulDB entry created
09/24/2026 VulDB entry last update
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Confirmed
CVE: CVE-2026-18857 (🔒)
GCVE (CVE): GCVE-0-2026-18857
GCVE (VulDB): GCVE-100-409365
Entry
Created: 09/24/2026 16:23Changes: 09/24/2026 16:23 (62)
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.