Maintained by Pétur Eyþórsson, Cristie Nordic. Last updated 2026-06-29.
This page tracks CVE-2026-12628 and related IBM Storage Protect and FlashCopy Manager advisories from the same research stream, tracked internally under the research label BUBBLEGUM. It is a factual reference for what is publicly known and what to do about it. It is not a technical write-up, so there is no proof of concept, packet detail, credential strings, or unpublished mechanics for related findings. For vendor-confirmed scope and fixes, rely on the IBM bulletin, and verify current values against IBM, CVE.org, and NVD when you read this.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NIBM's bulletin lists the affected supported products as IBM Storage Protect Client and Snapshot for Windows, versions 8.1.0.0 through 8.2.1.0.
The underlying code reaches back further. The hardcoded credential and the broken authentication have been present since IBM Tivoli Storage Manager 6.1.5.0, released in November 2011, and exist in every release from 6.1.5.0 onward. Out-of-support releases are affected too. They are outside IBM's supported-version advisory but still carry the code, so treat anything from 6.1.5.0 onward as vulnerable and plan upgrades where patching is not possible.
Exposure depends on a combination of factors, not simply on the product being installed. Prioritise a host when all of these apply:
TCPServeraddress FLASHCOPYMANAGER in the client options file);Standard IBM Storage Protect client-server backup paths should be assessed separately from the FlashCopy Manager and Snapshot path. In testing for this research, ordinary backup traffic to a real Storage Protect server did not show the same exposure pattern. Customers not using the affected configuration are lower priority for this specific issue. Verify versions, components, and configuration rather than assuming any deployment is clear, and avoid treating a deployment as definitively unaffected unless IBM states so.
A single fixed-port firewall rule is not sufficient on its own. Confirm the actual listeners on each host and restrict those.
Additional related findings have been reported to IBM. Technical details, identifiers, affected scope, severity, and mechanics for the unresolved issues are not published here while IBM assessment, fixes, or advisories are pending. Public entries will be added when IBM publishes advisories, or when safe defender guidance can be released without increasing customer exposure. This page does not list unpublished internal tracking IDs, expected CVEs, weakness classifications, or chaining relationships for unresolved findings.
CVE-2026-12628 is the first public advisory from this research stream. The remaining findings are under IBM handling, and their technical detail is withheld temporarily for customer protection. This page is updated as public advisories, fixes, mitigations, or safe defender guidance become available.