Skip to main content
Menu
CVEs

IBM Guardium Data Protection root privilege escalation in Collector setuid helper

Affects IBM Guardium Data Protection 12.2 Collector appliances through the SUID-root podman_wrapper binary. Fixed in 12.2.4.

CVE-2026-84087Published November 19, 2026, updated

7.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 12.2.4
Who is exposed
Specific setups only

Summary

IBM Guardium Data Protection contains a local privilege escalation flaw in a setuid-root helper binary on the Collector appliance. An attacker who already has low-privileged local access can exploit weak argument validation in that binary to run arbitrary commands as root and take full control of the appliance.

Written by a model

Original description

IBM Guardium Data Protection 12.2 is vulnerable to local privilege escalation via the SUID-root podman_wrapper binary on the Collector appliance. A local attacker with low-privileged access to the Collector can exploit insufficient argument validation in the SUID binary to execute arbitrary commands as root, resulting in full compromise of the Collector appliance.

Who should check

Teams running IBM Guardium Data Protection 12.2 Collector appliances.

“IBM Guardium Data Protection 12.2”

ibm.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects IBM Guardium Data Protection 12.2. Requires the SUID-root podman_wrapper binary on the Collector appliance.
  2. Upgrade to a fixed version: 12.2.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-84087 (IBM Guardium Data Protection Improper Privilege Management), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-84087 (entry last updated 2026-11-20):
Affected:
- IBM Guardium Data Protection: versions 12.2
Fixed versions: 12.2.4.
Conditions (all must be true for the bug to be hit):
- Affects IBM Guardium Data Protection 12.2. (source: https://www.ibm.com/support/pages/node/7297484)
- Requires the SUID-root podman_wrapper binary on the Collector appliance. (source: https://www.ibm.com/support/pages/node/7297484)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-84087 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-84087 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.ibm.com/support/pages/node/7297484
- https://www.cve.org/CVERecord?id=CVE-2026-84087
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-84087
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-84087"}.

Affected versions

cve.now Index

14Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 7.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Patchibm.com · support/pages/node/7297484
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-84087
RecordNVD · CVE-2026-84087

Questions about CVE-2026-84087

Is CVE-2026-84087 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The flaw is in the SUID-root podman_wrapper binary on the Collector appliance, and it can let an attacker execute arbitrary commands as root. The advisory says this can lead to full compromise of the Collector appliance.

Source: ibm.com, cve.org

Which versions are affected by CVE-2026-84087?

Guardium Data Protection: version 12.2.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory names IBM Guardium Data Protection 12.2 and the SUID-root podman_wrapper binary on the Collector appliance. To check a installation, confirm the installed Guardium Data Protection version on the Collector and whether it is 12.2.

Source: ibm.com, cve.org

How do I fix CVE-2026-84087?

Upgrade to IBM Guardium Data Protection 12.2.4, the fixed version named in the advisory.

Source: ibm.com, cve.org

No corrections so far. Something wrong on this page? Report an error.