Skip to content
High-Risk Vulnerability in IBM Guardium Data Protection Disclosed

High-Risk Vulnerability in IBM Guardium Data Protection Disclosed

First seen 20 Nov 2026, 17:17 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 20, 2026 at 17:18 UTC
  • •CVE-2026-84273 allows authenticated attackers to delete files on IBM Guardium appliances.
  • •The vulnerability has a CVSS score of 8.1, indicating a high risk level.
  • •Prompt remediation is advised, especially for organizations with exposed management interfaces.

IBM Guardium Data Protection 12.2 is affected by CVE-2026-84273, a path traversal vulnerability that allows authenticated attackers to delete arbitrary files on the appliance. The vulnerability has a CVSS score of 8.1, indicating a high operational risk. While there is no confirmed proof of concept or active exploitation reported, the risk remains significant due to the potential for disruption of monitoring and audit processes. Organizations with network-accessible management interfaces and datasource integrations are particularly vulnerable. IBM has released a fix for this issue, and prompt remediation is advised. Security teams should review logs for unusual activity and restrict access to the datasource functionality.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-19
CVE-2026-84273 published
IBM disclosed a path traversal vulnerability in Guardium Data Protection 12.2, allowing file deletion by authenticated users.
Ibm

More articles in this cluster (5)

Following this threat?

Track CVE-2022-35948 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of IBM Guardium are affected?
IBM Guardium Data Protection 12.2 is specifically mentioned as vulnerable.
Is there active exploitation of this vulnerability?
No confirmed active exploitation has been reported, but the risk remains high.
What immediate actions should organizations take?
Organizations should apply the vendor's fix promptly and restrict access to the datasource functionality.