CVE-2025-2947
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM i 7.6 contains a privilege escalation vulnerability where incorrect profile swapping in an OS command allows a malicious actor to elevate privileges from a standard user to root access on the host operating system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm IBM i version is 7.6Run command 'DSPSFWRSC' or 'WRKPRD' to display installed software and version. Look for '5770SS1' (IBM i) and verify version shows 7.6.Affected if The system shows IBM i version 7.6 (specifically 7.6.0 or 7.6.1) as the installed operating system.
-
Identify privileged OS commands accessible to standard usersReview commands with special authorities (like *ALLOBJ, *SECADM, *IOSYSCFG) that are available to non-privileged user profiles using 'WRKUSRPRF' and DSPUSRPRF options.Affected if Standard (non-privileged) user profiles have access to OS commands that perform profile swapping operations.
-
Check for unauthorized use of profile-swapping commandsReview job logs and security audit journal (QAUDJRN) for commands executed with switched profiles, particularly looking for entries with unexpected profile transitions.Affected if Audit logs show commands executing under different (elevated) user profiles from standard user sessions.
-
Verify user profile authorities to system command objectsUse 'WRKOBJ' / 'DSPOBJATR' on system command objects (*CMD) in QSYS library to check which user profiles have authority to execute privileged OS commands.Affected if Standard user profiles have authorities to execute commands capable of profile swapping that should be restricted to privileged profiles only.
You are affected if your IBM i system runs version 7.6 and standard (non-privileged) user profiles can access or have recently executed OS commands that perform profile swapping to elevate privileges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply IBM's security patch for CVE-2025-2947 to IBM i 7.6 immediately. Identify and restrict access to the vulnerable command until the patch is applied.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2947 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data