Skip to content
major vulnerability· requires attention

Enterprise data-protection product; authenticated RCE in IBM Guardium can lead to system compromise and data exposure across organizations.

Applications

CVE-2026-84106

8.9
High
EPSS 0.32%Sep 21, 2026

Authenticated RCE in IBM Guardium Data Protection 12.2 via web input sanitization flaw

common questions

Is CVE-2026-84106 being exploited?

Not confirmed. CVE-2026-84106 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-84106?

CVE-2026-84106 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-84106?

Not known from our data. No patch reference has been recorded for CVE-2026-84106, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-84106 affect?

CVE-2026-84106 affects IBM Guardium Data Protection 12.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84106?

Follow IBM advisory; apply vendor updates or restrict access to the management UI until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Guardium Data Protection 12.2
impact

Authenticated remote code execution (via web input/CWE-79) enabling full system compromise and potential data exfiltration.

action required

Immediate action required

affected versions
IBM Guardium Data Protection
  • affected12.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free