Skip to main content

IBM Storage Protect EUVDEUVD-2026-45307

| CVE-2026-13473 CRITICAL
Heap-based Buffer Overflow (CWE-122)
2026-07-17 psirt@us.ibm.com GHSA-9qhh-4vx4-2pqx
9.8
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.1 HIGH

Client-side heap overflow needs attacker-controlled server data or MITM position, so AC:H rather than AC:L; no auth/interaction assumed on the client side, full CIA impact via potential RCE.

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

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

6
Analysis Updated
Aug 11, 2026 - 23:43 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Aug 11, 2026 - 23:37 vuln.today
cvss_changed
Severity Changed
Aug 11, 2026 - 23:37 NVD
HIGH CRITICAL
CVSS changed
Aug 11, 2026 - 23:37 NVD
8.1 (HIGH) 9.8 (CRITICAL)
Analysis Generated
Jul 17, 2026 - 20:37 vuln.today
CVE Published
Jul 17, 2026 - 20:17 nvd
HIGH 8.1

DescriptionNVD

IBM Storage Protect Client 8.1.0.0 through 8.1.27.0, 8.1.27.1, and 8.2.0.0 through 8.2.1.0 IBM Storage Protect is vulnerable to a heap-based buffer overflow, caused by improper bounds checking. A remote attacker could overflow a buffer and execute arbitrary code on the system or cause the server to crash.

AnalysisAI

Heap-based buffer overflow in IBM Storage Protect Client (versions 8.1.0.0-8.1.27.1 and 8.2.0.0-8.2.1.0) lets a remote attacker corrupt heap memory through improper bounds checking, potentially achieving arbitrary code execution or crashing the affected process. The flaw carries a CVSS 3.1 base score of 9.8, but no public exploit identified at time of analysis and the EPSS probability is low (0.46%, 37th percentile). Note that the affected component is the backup Client, while the description references crashing 'the server,' introducing ambiguity about the true exploitation path.

Technical ContextAI

IBM Storage Protect (formerly Tivoli Storage Manager / IBM Spectrum Protect) is enterprise data-protection and backup software; the affected component here is the Storage Protect Client, which communicates with a Storage Protect server to move backup/restore data. The root cause is CWE-122 (heap-based buffer overflow): input is copied into a dynamically allocated heap buffer without adequate bounds checking, allowing an over-long or malformed field to write past the buffer and corrupt adjacent heap metadata or objects. Successful heap corruption of this type can be leveraged for control-flow hijacking (arbitrary code execution) or, more reliably, denial of service via crash. The CPE cpe:2.3:a:ibm:storage_protect:*:*:*:*:*:*:*:* confirms the IBM Storage Protect application as the affected product.

RemediationAI

Patch available per vendor advisory: upgrade the IBM Storage Protect Client to the fixed release referenced in IBM advisory https://www.ibm.com/support/pages/node/7279728 (the exact fixed version is not stated in the available data and should be confirmed directly from that advisory before deployment). Because the affected component is the client and the likely attack path involves malicious data from a server or network position, effective compensating controls until patching include restricting client connectivity so that Storage Protect clients only reach trusted, authenticated backup servers, enforcing TLS with certificate validation on client-server communications to prevent machine-in-the-middle injection, and segmenting the backup network to limit who can present data to clients - the trade-off being added configuration overhead and potential disruption to backup jobs if certificate or routing changes are misapplied. Do not treat absence of an exact version here as absence of a patch; the advisory URL is authoritative.

Share

EUVD-2026-45307 vulnerability details – vuln.today

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