CVE-2026-15065
Ibm Vios 4.1.0 – 4.1.0.50
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-15065 is a critical-severity Cleartext Storage of Sensitive Information (CWE-312) vulnerability in Ibm Vios. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSA Secrets (T1003.004); ranked in the top 50% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-28 (Protection of Information at Rest) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-62424
Vulnerability Data
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 NIM could allow a remote attacker to bypass security restrictions due to the exposure of intermediate certificate authority private keys in a publicly available update file.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 3 OS baselines
V14.2.8
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
SC-28 requires cryptographic or equivalent protection of sensitive data at rest, directly stopping cleartext storage in accessible resources.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Encryption and cryptographic controls for data-at-rest directly prevent cleartext storage of sensitive information.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
created from the owner's anchor; an owner grade is a row and does not wait for an instrument (Mythos 2026-09-29T15:58Z).
Code review and static analysis can identify cleartext-storage patterns while runtime and penetration tests can expose accessible plaintext stores, leaving a bounded remainder in opaque services, unexercised paths, and context-dependent sensitive-data flows.
A.5.17 mandates that passwords be stored in protected form (encrypted/hashed per approved cryptographic techniques) and transmitted securely, which removes the cleartext-storage weakness for authentication information specifically; however, CWE-312 covers all sensitive information (PHI, financial data, configuration secrets, etc.), and A.5.17's scope is limited to authentication information, so it addresses only a portion of the weakness class.
A.7.10(d) requires cryptographic protection of information on removable storage media when confidentiality matters, so applying the clause to a system that previously stored sensitive data in cleartext on such media removes that subset of CWE-312 instances; the remainder is the broader class of cleartext storage in databases, cookies, memory, config files, and other non-storage-media resources that A.7.10 does not reach.
A.8.1 mandates access controls (g), physical protection (c), and remote disabling/deletion/lockout (j) for endpoint devices, which block some exploitation of cleartext storage by preventing unauthorized access to the device; however, the weakness remains present in the storage medium and can be exploited by removing the drive or bypassing access controls, and the storage device encryption item (h) is a removes/prevents mechanism rather than a blocks mechanism.
A.8.10 mandates deletion of information no longer required, which removes the cleartext-storage weakness for that subset (including obsolete copies, temporary files, and data past retention). However, A.8.10 does not address the core CWE-312 issue of sensitive information that must be retained but is stored unencrypted — that requires encryption (A.8.24), not deletion. The remainder is bounded and nameable: data still required for business purposes.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (1 rule)
- V-248525 All OL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at-rest protection. blocks CWE-312
Oracle Linux 9 (1 rule)
- V-271756 OL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-312
RHEL 8 (1 rule)
- V-230224 All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-312