# CVE-2026-12628: Hardcoded credential in the IBM Storage Protect Snapshot For Windows leads to unauthorized access to system

> Hardcoded credentials in IBM Storage Protect allow remote attackers to bypass authentication and access protected system resources.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-5vh7-hcv2-h9gx

## What is CVE-2026-12628?

CVE-2026-12628 is a critical vulnerability in IBM Storage Protect Client, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Storage Protect Client 8.1.0.0 through 8.2.1.0 and IBM Storage Protect Snapshot For Windows 8.1.0.0 through 8.2.1.0 could allow a remote attacker to bypass authentication due to the use of a hardcoded credential in the FlashCopy Manager (FCM) authentication mechanism. The application contains a static credential embedded in multiple authentication code paths, and does not properly validate authentication responses, which may allow an unauthenticated attacker to establish a trusted session and access protected services. This vulnerability affects client components across multiple versions and may allow an attacker to impersonate legitimate clients, potentially leading to unauthorized access to system resources.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-12628?

It affects 1 product.


Products: Ibm Storage Protect.

## How do I fix CVE-2026-12628?

No fix has been published for CVE-2026-12628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12628 being exploited?

There is no known exploitation of CVE-2026-12628 in the wild and no public exploit code.

## Other vulnerabilities in IBM Storage Protect Client

- [CVE-2023-35897](https://insights.sbomify.com/CVE-2023-35897/): IBM Spectrum Protect code execution (high 8.4)
- [CVE-2026-13473](https://insights.sbomify.com/CVE-2026-13473/): IBM Storage Protect Client is vulnerable to Heap-Based Buffer Overflow (high 8.1)
- [CVE-2024-38320](https://insights.sbomify.com/CVE-2024-38320/): IBM Storage Protect for Virtual Environments: Data Protection for VMware information disclosure (medium 5.9)
- [CVE-2023-40368](https://insights.sbomify.com/CVE-2023-40368/): IBM Storage Protect information disclosure (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12628 and fix it if it is affected.

What it is: CVE-2026-12628 is a critical vulnerability in IBM Storage Protect Client, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12628 in the wild and no public exploit code.

Affected product: IBM Storage Protect Client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12628/ (Markdown: https://insights.sbomify.com/CVE-2026-12628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12628
- OSV: https://osv.dev/vulnerability/CVE-2026-12628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12628/
Summaries are generated and may contain mistakes; the official description above is the record.