CVE-2026-4932: This Power System update is being released to address Insufficient Entropy
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
IBM PowerVM Hypervisor FW1110.00 through FW1110.20, and FW1060.00 through FW1060.71 could allow an attacker with physical access to the Transparent Memory Encryption (TME) hardware to decrypt encrypted memory due to insufficient cryptographic entropy.
- Published
- Jul 28, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-331
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.6
- CNA · ibm
- 4.2
- 0.4 point gap
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ibm | power system s1122 (9824-22a) firmware | cpe:2.3:o:ibm:power_system_s1122_(9824-22a)_firmware |
| ibm | power system s1122 (9824-22a) | cpe:2.3:h:ibm:power_system_s1122_(9824-22a) |
| ibm | power system s1124 (9824-42a) firmware | cpe:2.3:o:ibm:power_system_s1124_(9824-42a)_firmware |
| ibm | power system s1124 (9824-42a) | cpe:2.3:h:ibm:power_system_s1124_(9824-42a) |
| ibm | power system s1122s (9824-22b) firmware | cpe:2.3:o:ibm:power_system_s1122s_(9824-22b)_firmware |
| ibm | power system s1122s (9824-22b) | cpe:2.3:h:ibm:power_system_s1122s_(9824-22b) |
| ibm | power system s1114 (9824-41b) firmware | cpe:2.3:o:ibm:power_system_s1114_(9824-41b)_firmware |
| ibm | power system s1114 (9824-41b) | cpe:2.3:h:ibm:power_system_s1114_(9824-41b) |
| ibm | power system l1122 (9856-22h) firmware | cpe:2.3:o:ibm:power_system_l1122_(9856-22h)_firmware |
| ibm | power system l1122 (9856-22h) | cpe:2.3:h:ibm:power_system_l1122_(9856-22h) |
| ibm | power system l1124 (9856-42h) firmware | cpe:2.3:o:ibm:power_system_l1124_(9856-42h)_firmware |
| ibm | power system l1124 (9856-42h) | cpe:2.3:h:ibm:power_system_l1124_(9856-42h) |
and 22 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm power system e1050 (9043-mrx) firmwarefw1060.00 and later · before fw1060.72
- ibm power system e1080 (9080-hex) firmwarefw1060.00 and later · before fw1060.72
- ibm power system e1150 (9043-mru) firmwarefw1110.00 and later · before fw1110.30
- ibm power system e1180 (9080-heu) firmwarefw1110.00 and later · before fw1110.30
- ibm power system l1022 (9786-22h) firmwarefw1060.00 and later · before fw1060.72
- ibm power system l1024 (9786-42h) firmwarefw1060.00 and later · before fw1060.72
- ibm power system l1122 (9856-22h) firmwarefw1110.00 and later · before fw1110.30
- ibm power system l1124 (9856-42h) firmwarefw1110.00 and later · before fw1110.30
- ibm power system s1012 (9028-21b) firmwarefw1060.00 and later · before fw1060.72
- ibm power system s1014 (9105-41b) firmwarefw1060.00 and later · before fw1060.72
- ibm power system s1022 (9105-22a) firmwarefw1060.00 and later · before fw1060.72
- ibm power system s1022s (9105-22b) firmwarefw1060.00 and later · before fw1060.72
- ibm power system s1024 (9105-42a) firmwarefw1060.00 and later · before fw1060.72
- ibm power system s1114 (9824-41b) firmwarefw1110.00 and later · before fw1110.30
- ibm power system s1122 (9824-22a) firmwarefw1110.00 and later · before fw1110.30
- ibm power system s1122s (9824-22b) firmwarefw1110.00 and later · before fw1110.30
- ibm power system s1124 (9824-42a) firmwarefw1110.00 and later · before fw1110.30
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM PowerVM Hypervisor
- FW1110.00 and later · up to and including FW1110.20affected · semver
- FW1060.00 and later · up to and including FW1060.71affected · semver
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-7868This Power System update is being released to address incorrect authorization35Monitor
- CVE-2026-11885Power System update in Buffer Copy33Monitor
- CVE-2026-17503This Power System update is being released to address20Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-8058Jul 28, 2026 · This Power System update is being released to address a sensitive information disclosure19Monitor
- Later →CVE-2026-17413Sep 24, 2026 · This Power System update is being released to address20Monitor
- Later →CVE-2026-17504Sep 24, 2026 · This Power System update is being released to address17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0667 · Jul 29, 2026(IBM Çoklu Ürün Güvenlik Bildirimi)
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-331 · Insufficient EntropyCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.