dbcve.org
Storage FusionApplication · Ibm

CVE-2025-36222

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-11
Fix available
A fix is available. Upgrade to 2.11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Fusion 2.2.0 through 2.10.1, IBM Fusion HCI 2.2.0 through 2.10.0, and IBM Fusion HCI for watsonx 2.8.2 through 2.10.0 uses insecure default configurations that could expose AMQStreams without client authentication that could allow an attacker to perform unauthorized actions.

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 Fusion products (versions 2.2.0-2.10.1) ship with insecure default configurations that expose AMQStreams (Apache Kafka) without client authentication enabled. This allows unauthenticated attackers to connect to the message broker and potentially publish, consume, or manipulate messages across the event streaming infrastructure.

MitigationEnable client authentication on AMQStreams (e.g., SASL/SCRAM or TLS certificate authentication) and review network exposure to prevent unauthorized access to the broker endpoints.

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 FusionApplication
Affected:>= 2.2.0, < 2.11.0
Storage Fusion HciApplication
Affected:>= 2.2.0, < 2.11.0
Storage Fusion Hci For WatsonxApplication
Affected:>= 2.8.2, < 2.11.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
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 checks

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

  1. Confirm IBM Fusion product and version
    Identify which IBM Fusion product is installed (IBM Storage Fusion, IBM Storage Fusion HCI, or IBM Storage Fusion HCI for Watsonx) and determine the exact version using product-specific commands or by inspecting installed packages
    Affected if The installed version is >= 2.2.0 and < 2.11.0
  2. Verify AMQStreams deployment
    Determine whether AMQStreams (Apache Kafka) components are deployed and running in the IBM Fusion environment
    Affected if AMQStreams/Kafka is deployed and active in the environment
  3. Inspect Kafka broker authentication settings
    Examine the AMQStreams Kafka broker configuration files to check whether client authentication is enabled. Look for SASL/SCRAM, TLS certificate authentication, or other authentication mechanisms in the broker configuration
    Affected if Client authentication is not configured or explicitly disabled on the Kafka broker
  4. Verify client authentication enforcement
    Check if the Kafka broker is configured to require authentication from clients attempting to connect. This may involve reviewing broker security settings, listener configurations, or authentication protocol settings
    Affected if The broker accepts unauthenticated client connections or has authentication set to disabled or optional

The environment is affected if IBM Storage Fusion (or variant) version is between 2.2.0 and 2.10.1 inclusive, AMQStreams/Kafka is deployed, and client authentication is not enabled on the broker.

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
Upgrade available Upgrade to 2.11.0 or later
Fixed in 2.11.0
Interim mitigation

Enable client authentication on AMQStreams (e.g., SASL/SCRAM or TLS certificate authentication) and review network exposure to prevent unauthorized access to the broker endpoints.

Recommended fix High confidence

IBM Storage Fusion 2.11.0 (and later) for all affected product variants

  1. Review the IBM Storage Fusion, Storage Fusion HCI, or Storage Fusion HCI for Watsonx upgrade documentation for your specific product
  2. Plan an upgrade window and ensure appropriate backups are in place
  3. Download IBM Storage Fusion version 2.11.0 (or later) from IBM Fix Central or your entitled IBM repository
  4. Follow IBM's documented upgrade procedure for your specific Storage Fusion product
  5. After upgrade, verify that AMQStreams is configured with client authentication enabled per IBM's security best practices
  6. Confirm the version upgrade was successful and the vulnerability is resolved
Caveat Review IBM's release notes for 2.11.0 for any migration or compatibility considerations specific to your deployment

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

Fix this in Storage Fusion Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36222 — 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-36222 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