CVE-2025-36250
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 AIX 7.2, and 7.3 and IBM VIOS 3.1, and 4.1 NIM server (formerly known as NIM master) service (nimesis) could allow a remote attacker to execute arbitrary commands due to improper process controls. This addresses additional attack vectors for a vulnerability that was previously addressed in CVE-2024-56346.
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 · high confidenceA remote command injection vulnerability in the IBM NIM (Network Installation Management) server service (nimesis) on AIX 7.2/7.3 and VIOS 3.1/4.1 allows unauthenticated attackers to execute arbitrary commands due to improper process controls. This is an update to CVE-2024-56346 addressing additional attack vectors.
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= 3.1.0= 4.1.0= 7.2= 7.3CVSS 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 system is AIX or VIOSRun 'oslevel' on AIX or 'ioslevel' on VIOS to identify the operating system and versionAffected if The system is not running AIX 7.2, AIX 7.3, VIOS 3.1.0, or VIOS 4.1.0 - these are the only affected platforms
-
Identify the exact OS versionRun 'oslevel -s' on AIX or 'ioslevel' on VIOS and compare the output to the affected versions: AIX 7.2, AIX 7.3, VIOS 3.1.0, VIOS 4.1.0Affected if The version matches exactly one of the affected versions listed (7.2, 7.3, 3.1.0, or 4.1.0)
-
Check if NIM service (nimesis) is runningRun 'lssrc -a | grep nimesis' or 'lssrc -s nimesis' to determine if the NIM server service is active on the systemAffected if The nimesis service is listed as active or started - this is the vulnerable component
-
Verify NIM network exposureRun 'netstat -an | grep 1058' or 'netstat -an | grep nimesis' to check if the NIM service port (default 1058) is listening on network interfaces accessible to untrusted networksAffected if The NIM service is listening on a port accessible from untrusted/networked interfaces rather than only localhost or restricted admin networks
A system is affected if it runs AIX 7.2, AIX 7.3, VIOS 3.1.0, or VIOS 4.1.0, has the NIM (nimesis) service running, and has the service exposed to accessible network interfaces.
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 security patches for this vulnerability to the affected AIX and VIOS systems, and restrict network access to the NIM service to minimize exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36250 — 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-36250 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