Skip to content
major vulnerability· requires attention

Critical stored XSS in a widely used enterprise DB security product (IBM Guardium) that can enable admin account compromise and data exposure.

Web

CVE-2026-84244

9.3
Critical
EPSS 0.18%Patch availableOct 9, 2026

Stored XSS in IBM Guardium 12.2 Quick Search allows script execution in user browsers.

common questions

Is CVE-2026-84244 being exploited?

Not confirmed. CVE-2026-84244 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.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-84244?

CVE-2026-84244 is rated Critical with a CVSS score of 9.3. 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-84244?

Yes. A fix has been recorded for CVE-2026-84244. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84244 affect?

CVE-2026-84244 affects IBM Guardium Data Protection 12.2, Guardium Web UI (Quick Search results grid). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84244?

Apply IBM advisory patch ASAP; restrict UI access and rotate credentials.

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.2Guardium Web UI (Quick Search results grid)
impact

Stored XSS can run arbitrary JS in authenticated users' browsers, enabling session hijack, credential theft, or admin account takeover.

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