CVE-2025-36119
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.3, 7.4, 7.5, and 7.6 is affected by an authenticated user obtaining elevated privileges with IBM Digital Certificate Manager for i (DCM) due to a web session hijacking vulnerability. An authenticated user without administrator privileges could exploit this vulnerability to perform actions in DCM as an administrator.
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 confidenceIBM Digital Certificate Manager (DCM) for IBM i contains a session hijacking vulnerability allowing an authenticated non-administrative user to hijack an administrator's web session and perform actions with administrator privileges, achieving privilege escalation.
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.3= 7.4= 7.5= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify IBM i OS versionCheck the installed IBM i operating system version using the DSPSYSVAL command (SYSVAL 502) or WRKSYSSTS to confirm if it is 7.3, 7.4, 7.5, or 7.6Affected if The OS version matches 7.3, 7.4, 7.5, or 7.6 - only these versions contain the vulnerable DCM code
-
Confirm DCM is installedQuery the installed licensed programs on the system using WRKOBJ or the LPP (Licensed Program Product) information to verify Digital Certificate Manager (product identifier 5770-SS1 option 34 or similar DCM-related option) is installedAffected if DCM is installed and running on an affected IBM i version (7.3-7.6)
-
Check DCM web interface accessibilityVerify whether the DCM web-based interface (typically accessed via HTTP/HTTPS on port 2001 or similar IBM i web services ports) is enabled and accessible to non-administrative usersAffected if The DCM web interface is accessible to authenticated non-administrative users on the network
-
Review DCM user session configurationsInspect DCM user profiles and their associated privileges within the DCM administration console to identify if non-administrative users have active sessions that could be exploited for session hijackingAffected if Non-administrative user accounts exist with DCM access and can potentially intercept or hijack administrator sessions
A user is affected if their IBM i system runs version 7.3, 7.4, 7.5, or 7.6 AND has Digital Certificate Manager installed with its web interface accessible to non-administrative users.
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 patches for this vulnerability to IBM i systems running DCM. Until patched, restrict DCM access to trusted administrators and implement session monitoring to detect anomalous administrative actions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36119 — 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-36119 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