IBM Power Firmware up to FW1060.80/FW1110.30/FW1120.00 information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in IBM Power Firmware up to FW1060.80/FW1110.30/FW1120.00. It has been classified as problematic. Affected is an unknown function. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2026-19321. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability, which was classified as problematic, has been found in IBM Power Firmware up to FW1060.80/FW1110.30/FW1120.00. This issue affects an unknown code block. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
IBM Power Firmware FW1120.00, FW1110.00 through FW1110.30, and FW1060.00 through FW1060.80 is affected by a vulnerability in the host firmware. An attacker with service access to the service processor can supply a carefully crafted command that could leak the contents of hardware registers that should be inaccessible to the service processor. Successful exploitation could result in limited confidentiality or availability impacts to the affected host system.
The advisory is shared at ibm.com. The identification of this vulnerability is CVE-2026-19321 since 08/07/2026. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. 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 08/19/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
Type
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
- 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
- FW1120
License
Website
- Vendor: https://www.ibm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.5
VulDB Base Score: 2.3
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.7
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
EPSS Score: 🔒
EPSS Percentile: 🔒
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/07/2026 CVE reserved08/19/2026 Advisory disclosed
08/19/2026 VulDB entry created
08/19/2026 VulDB entry last update
Sources
Vendor: ibm.comAdvisory: ibm.com
Status: Confirmed
CVE: CVE-2026-19321 (🔒)
GCVE (CVE): GCVE-0-2026-19321
GCVE (VulDB): GCVE-100-393293
Entry
Created: 08/19/2026 20:55Changes: 08/19/2026 20:55 (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.