dbcve.org
Storage VirtualizeApplication · Ibm

CVE-2025-36118

HIGH · 7.5 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
IBM Storage Virtualize 8.4, 8.5, 8.7, and 9.1 IKEv1 implementation allows remote attackers to obtain sensitive information from device memory via a Security Association (SA) negotiation request.

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 confidence

IBM Storage Virtualize versions 8.4, 8.5, 8.7, and 9.1 contain a vulnerability in the IKEv1 implementation where remote attackers can obtain sensitive information from device memory by sending specially crafted Security Association (SA) negotiation requests. This is an unauthenticated information disclosure flaw affecting the VPN/key exchange functionality.

MitigationApply IBM's available patch or firmware update for Storage Virtualize. If immediate patching is not possible, restrict IKEv1 protocol traffic at network boundaries using firewalls or IPS filters to block unauthenticated SA negotiation requests from untrusted networks.

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
Storage VirtualizeApplication
Affected:= 8.4.0.0= 8.5.0.0= 8.7.0.0= 9.1.0.0

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the IBM Storage Virtualize version
    Access the storage system management CLI (ssh to the management IP) and run the command to display system version, typically 'lsversion' or 'system -v' or check via the GUI under System > Overview
    Affected if The installed version is exactly 8.4.0.0, 8.5.0.0, 8.7.0.0, or 9.1.0.0
  2. Determine if IKEv1 protocol is enabled
    Access the storage system configuration and review the IPSec/IKE settings. In the CLI, this may be found under 'ipsec' or 'ike' configuration context, or via the GUI under Network > IPSec/VPN settings
    Affected if IKEv1 protocol is enabled or configured on the system (IKEv2 alone is not affected)
  3. Check for active VPN tunnels using IKEv1
    List active IPsec VPN tunnels or IKE Security Associations using command such as 'ikeSaList' or 'ipsec - status' in the storage system CLI
    Affected if Any VPN tunnels are established or configured using IKEv1 protocol
  4. Verify network exposure of IKE ports
    Review firewall rules or network configuration to determine if UDP ports 500 (IKE) and 4500 (NAT-T) are exposed to untrusted networks
    Affected if The IKEv1 ports (500/UDP and 4500/UDP) are accessible from external or untrusted network segments

The environment is affected if the installed IBM Storage Virtualize version is 8.4.0.0, 8.5.0.0, 8.7.0.0, or 9.1.0.0 AND the IKEv1 protocol is enabled or VPN tunnels using IKEv1 are configured, with the IKE ports potentially exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's available patch or firmware update for Storage Virtualize. If immediate patching is not possible, restrict IKEv1 protocol traffic at network boundaries using firewalls or IPS filters to block unauthenticated SA negotiation requests from untrusted networks.

Recommended fix Moderate confidence

IBM Storage Virtualize 9.2.0.0 or later

  1. Back up the IBM Storage Virtualize configuration data
  2. Download IBM Storage Virtualize version 9.2.0.0 or later from IBM Fix Central
  3. Schedule a maintenance window for the upgrade
  4. Install the upgrade following IBM's standard upgrade procedures for Storage Virtualize
  5. After upgrade, verify the IKEv1 vulnerability is remediated by confirming SA negotiation no longer exposes memory contents
  6. Test critical storage operations to ensure normal functionality
Caveat Major version upgrades may introduce configuration changes; review IBM release notes for Storage Virtualize 9.2 for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storage Virtualize Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36118 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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