IBM has patched 14 vulnerabilities in Security Guardium Data Protection 12.2, including CVE-2026-84236, an unauthenticated remote code execution flaw rated CVSS 9.8. The fixes ship in version 12.2.4, and no exploitation has been confirmed.
CVE-2026-84236 Deserialization Bug Allows Unauthenticated Code Execution
CVE-2026-84236 is an insecure deserialization flaw in the SharePoint Tap Multicast Transceiver component. It lets an unauthenticated attacker execute code remotely and scores 9.8 on the CVSS scale.
IBM’s bulletin and the 12.2.4 release arrived together. Four of the 14 flaws are critical, with scores between 9.1 and 9.8.
Other Critical Guardium Flaws: SQL Injection and Missing Authentication
CVE-2026-87977, also scored 9.8, is a SQL injection in the edge-controller component. CVE-2026-82339, scored 9.1, is a missing authentication flaw in the S-TAP RelayService that allows an attacker to forge audit events. Forged audit events are significant for a product whose purpose is to record database activity.
High-Severity Path Traversal and Local Root Bugs
CVE-2026-84273, scored 8.1, is a path traversal flaw that permits file deletion. CVE-2026-84087, scored 7.8, allows local privilege escalation to root through podman_wrapper.
Why Guardium Is a High-Value Target
Guardium Data Protection is a tool used by banks, hospitals and government agencies to monitor sensitive databases. Compromising it could give an attacker control over a system that holds visibility into some of an organization’s most sensitive data stores, and the flaws that allow audit-event forgery bear directly on the integrity of that monitoring.
Exploitation Status and Public Exploits
No exploitation and no public exploits have been confirmed for any of the flaws. That leaves the 12.2.4 release as a proactive fix rather than a response to an ongoing campaign, though the unauthenticated nature of the top-scoring bugs makes them attractive once technical details circulate.
Upgrade Path to Version 12.2.4
IBM’s response is to upgrade to 12.2.4. The affected release line is Guardium Data Protection 12.2, and the single fixed version covers all 14 flaws in the bulletin, which simplifies the remediation decision for administrators of that line.
Security Monitoring Infrastructure as Attack Surface
The set of flaws spans several component families: deserialization, SQL injection, missing authentication, path traversal and local privilege escalation. A security product that monitors databases is itself a high-privilege system connected to those databases, and the unauthenticated critical flaws mean an attacker who can reach the vulnerable components would not need credentials first. The forged-audit-event weakness in S-TAP RelayService stands out because it could let an attacker corrupt the records that defenders rely on to investigate database activity.
Component Breakdown of the Four Critical Guardium Flaws
The four critical flaws sit in different components, so the bulletin does not point to one weak module. The deserialization bug is in the SharePoint Tap Multicast Transceiver, the SQL injection is in the edge-controller, and the missing authentication is in the S-TAP RelayService. The fourth critical issue is also scored in the 9.1 to 9.8 band reported for the set. Below them, the path traversal flaw permits file deletion, and the local root bug runs through podman_wrapper, giving a user with local access a route to root. IBM confirms no exploitation and no public exploits, and its remediation covers every listed flaw in a single version, 12.2.4.
The 12.2.4 release is the single fixed version named for Guardium Data Protection 12.2. The reporting does not identify any customers affected, and it does not say that any attacker has attempted to use the flaws. For an organization running the product to watch regulated databases, the combination of unauthenticated critical flaws and the forged audit-event weakness makes the update a priority even without evidence of attacks.
