Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-2947 is a high-severity Insecure Preserved Inherited Permissions (CWE-278) vulnerability in Ibm I. Its CVSS base score is 7.2 (High).
Operationally, ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-11553
Vulnerability Data
IBM i 7.6 contains a privilege escalation vulnerability due to incorrect profile swapping in an OS command. A malicious actor can use the command to elevate privileges to gain root access to the host operating system.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requires that only the minimum necessary permissions are granted, preventing automatic inheritance of excessive rights.
Enforces approved authorizations on objects instead of blindly preserving insecure inherited permissions from external sources such as archives.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege permission policies and reviews directly prevents inheritance of insecure permissions from archives or copies.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access control policies can require explicit permission review on object creation or copy, reducing inherited insecure permissions.
Managing access rights includes reviewing and adjusting permissions when objects are copied or inherited.
Secure development lifecycle practices include permission handling requirements that prevent insecure inherited permissions in new code.
Secure coding standards can mandate explicit permission setting instead of relying on inherited defaults.
Information access restriction mechanisms can enforce least-privilege checks during object creation or archive extraction.
Configuration management can define secure default permissions and prevent insecure inheritance during deployment or copy operations.