CVE-2026-84057 is a high severity (8.1) OS command injection flaw in IBM Guardium Data Protection 12.2.2 and 12.1. A remote attacker could run arbitrary commands because special elements are not neutralized in an operating system command. IBM's fix is the set of patches in bulletin 7288832: Edge 12.0p15004, 12.0p147 and 12.0p150.
What's affected
IBM's bulletin 7288832 lists IBM Guardium Data Protection 12.2.2 (edge component) and 12.1 (Guardium appliance) as affected. IBM names three patches for all affected versions: the Edge patch 12.0p15004, patch 12.0p147 and patch 12.0p150. IBM lists no workarounds or mitigations.
The bulletin was published on 8 October 2026 and modified on 14 October 2026. It also lists other vulnerabilities. Read it for the full set.
How to check if you're exposed
Check which Guardium version and patch level each node runs, and which nodes are edge deployments. Compare to the three patches in the bulletin. Which patch applies depends on the component, so follow the bulletin's links for your deployment.
Also check who can reach the management interfaces. The record describes a remote attacker, so any network path to a Guardium management surface counts as exposure.
What to do now
- List Guardium nodes on 12.2.2 and 12.1, and note which are edge deployments.
- Apply the patches named in IBM bulletin 7288832: Edge 12.0p15004, 12.0p147 and 12.0p150, as they apply to your nodes.
- Restrict network access to Guardium management interfaces to administrators.
- Back up configuration before patching.
- Confirm patch levels on every node and review logs for unexpected file or command activity.
Why it matters
The weakness is CWE-78, improper neutralization of special elements used in an OS command. Input is included in a command line without being made safe.
IBM does not give the entry point in the record. The vector marks attack complexity as high and no privileges required, with high impact across the board. The record is not flagged in CISA's KEV catalog, and the bulletin does not report exploitation.
Quick check
Is there a configuration change that avoids this?
IBM lists no workarounds or mitigations in the bulletin. Patching is the listed remedy.
Sources
Last reviewed: 19 October 2026.
