Skip to main content

IBM Storage Scale EUVDEUVD-2026-58361

| CVE-2026-13460 HIGH
Use of Hard-coded Credentials (CWE-798)
2026-08-13 ibm GHSA-xr96-mx7v-w32h
7.5
CVSS 3.1 · Vendor: ibm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify network-accessible Storage Scale GUI endpoint
  2. Exploit
    Obtain hardcoded token from source or binary
  3. Execution
    Issue authenticated REST API requests using token
  4. Impact
    Access cluster management data and inter-node communication channels

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network-level reachability to the IBM Storage Scale GUI service port on an affected cluster node running versions 5.2.3.0-5.2.3.8 or 6.0.0.0-6.0.1.0. The hardcoded token is specifically used for inter-node REST API authentication between GUI instances - exploitation targets the GUI REST API, not the underlying GPFS data path or file system protocol directly. No authentication credentials beyond the static hardcoded token are required per the CVSS PR:N vector; the token is uniform across all affected deployments and cannot be rotated per-installation. Exploitation is limited to environments where the GUI component is deployed and the REST API port is network-accessible; environments that restrict GUI access to isolated management networks or disable the GUI entirely are not exposed via this vector.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N scores 7.5 High, reflecting unauthenticated network exploitation with high confidentiality impact at low complexity - a combination that warrants prompt remediation. The PR:N designation is technically accurate because the hardcoded token functionally bypasses the normal authentication layer: knowing the token is equivalent to holding a valid credential, and that token is uniform across all vulnerable deployments. No EPSS data was provided, and this CVE does not appear in CISA's KEV catalog, indicating no confirmed active exploitation at time of analysis. That said, the absence from KEV should not breed complacency - even a mid-sized municipal IT team in bytom operating IBM Storage Scale for shared research or administrative storage would face full cluster API exposure if the GUI is reachable on the management network. The confidentiality-only CVSS impact (I:N, A:N) may understate practical risk: authenticated REST API access in a storage cluster GUI could enable enumeration of node topology, credential harvesting from configuration endpoints, or reconnaissance enabling follow-on attacks, even if direct write exploitation is not captured in the base score.

Exploit ScenarioDerived

An attacker with network access to the Storage Scale GUI REST API port identifies the hardcoded token by inspecting the publicly available IBM Storage Scale source or binary package, then issues authenticated REST API requests using that token to enumerate cluster node configuration, extract sensitive administrative data, or impersonate a GUI node in inter-node communication. No public proof-of-concept exploit has been identified at time of analysis, but the low complexity (AC:L, PR:N) means exploitation requires only token knowledge and TCP connectivity to the GUI service port.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 13, 2026

IBM Storage Scale GUI versions 5.2.3.0-5.2.3.8 and 6.0.0.0-6.0.1.0 ship with a hardcoded authentication token embedded in source code, granting any network-reachable attacker the ability to authenticate to the REST API and inter-node cluster communication channels without valid credentials. The static nature of the token means it is identical across every affected deployment, making a single disclosure universally exploitable against all unpatched instances. IBM has released a patch via advisory 7283308, and no public exploit or CISA KEV listing has been identified at time of analysis.

RemediationAI

IBM has released a patch addressing this vulnerability; the authoritative fixed version details and upgrade instructions are available at https://www.ibm.com/support/pages/node/7283308, and administrators should consult this advisory directly since the exact patched version string was not independently confirmed in the available data. As an immediate compensating control prior to patching, restrict network access to the Storage Scale GUI and its REST API port using firewall rules or network segmentation, limiting reachability exclusively to trusted management hosts or VLANs - note this does not eliminate the hardcoded token but substantially reduces the attack surface by preventing external access. If inter-node GUI REST API communication is not operationally required in a given environment, disabling or binding the service to loopback or a dedicated management interface is a viable short-term measure, though this may impact cluster management functionality and should be validated against operational requirements before implementation.

Affected VersionsENISA

Storage Scale 5.2.3.0 ≤5.2.3.8
Storage Scale 6.0.0.0 ≤6.0.1.0

Affected Packages

euvd storage_scale no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

IBM Storage Scale (formerly IBM Spectrum Scale / GPFS) is an enterprise parallel file system used in HPC and large-scale storage environments. The vulnerability resides in the GUI component, which manages cluster administration and coordinates inter-node communication via a REST API. CWE-798 (Use of Hard-coded Credentials) identifies the root cause: a static token baked into the application source code at build time, used as a shared secret for both inter-node cluster communication and REST API authentication between GUI instances. Because the token is static and uniform across all affected installations - spanning CPE cpe:2.3:a:ibm:storage_scale:*:*:*:*:*:*:*:* - it cannot be rotated, revoked, or uniquely scoped per deployment. An attacker who obtains the token through source inspection, binary extraction, or disclosure can replay it against any vulnerable GUI endpoint to impersonate a legitimate cluster node.

Know when Storage Scale gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ibm) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Network-accessible REST API with a uniform hardcoded token effectively negates authentication (PR:N); only confidentiality impact applies as no write or availability effects are described.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

IBM Storage Scale 5.2.3.0 through 5.2.3.8, and 6.0.0.0 through 6.0.1.0 GUI contains a hardcoded token in the source code, which was used for inter-node cluster communication and REST API authentication between GUI.

Executive ViewAI

Why It Matters

IBM Storage Scale GUI versions 5.2.3.0 through 6.0.1.0 contain hardcoded authentication tokens in source code that enable any network-reachable attacker to access REST API and inter-node cluster communication without providing valid credentials. The static, universal nature of the token affects all unpatched deployments identically, creating uniform vulnerability across organizations. Leadership should prioritize remediation to prevent unauthorized access to mission-critical storage infrastructure and data.

Business Impact: High
Compensating Controls

Apply vendor patch per IBM advisory 7283308.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Medium
enterprise HPC and parallel storage platform, moderately deployed
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy