How severe is CVE-2026-84244?

CVE-2026-84244 has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2026-84244?

CVE-2026-84244 affects the following products: ibm guardium data protection.

How do I patch CVE-2026-84244?

No patch has shipped for CVE-2026-84244 yet — track the ibm guardium data protection advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2026-84244 across my infrastructure?

Inventory every ibm guardium data protection deployment and check each version against the affected-products list above.

How do I mitigate CVE-2026-84244 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2026-84244 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-84244 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-84244?

CVE-2026-84244 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2026-84244?

CVE-2026-84244 affects ibm guardium data protection (2 versions, e.g. 12.2, 12.2.0). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-84244 published, and has it been updated?

CVE-2026-84244 was published on October 8, 2026 and was last updated on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

CRITICAL severity

CVE-2026-84244 — Guardium Data Protection

CRITICAL

CVE-2026-84244 is a critical-severity (CVSS 9.3) Cross-site Scripting (XSS) vulnerability in ibm guardium data protection. No vendor fix is recorded yet; mitigation options are listed below.

IBM Guardium Data Protection 12.2 IBM Security Guardium Data Protection is vulnerable to stored cross-site scripting (XSS) in the Quick Search results grid. An unauthenticated attacker…

Published

Oct 8, 2026

Updated

Oct 8, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-84244.

Description

IBM Guardium Data Protection 12.2 IBM Security Guardium Data Protection is vulnerable to stored cross-site scripting (XSS) in the Quick Search results grid. An unauthenticated attacker who can influence monitored database traffic could execute malicious script in the browser of an authenticated Guardium user.

Affected Products

1 product · 2 configurations

Application

guardium data protectionibm

2 versions

12.212.2.0

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every ibm guardium data protection deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2026-84244 yet — track the ibm guardium data protection advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2026-84244 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works