Critical CVSS 9.8 Security news

IBM Guardium Data Protection 12.2: unauthenticated critical flaws allow code execution and forged audit records

On 19 November 2026 IBM published a security bulletin for Guardium Data Protection 12.2 covering fourteen vulnerabilities. Three are critical and need no account: insecure deserialization (CVE-2026-84236, CVSS 9.8) leads to code execution, SQL injection (CVE-2026-87977, 9.8) exposes database contents, and missing authentication (CVE-2026-82339, 9.1) lets attackers inject forged audit events. Version 12.2.4 fixes them; IBM reports no exploitation.

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

Critical: IBM Guardium Data Protection, CVE-2026-84236, CVSS 9.8

Key points

  • CVE-2026-84236 (CVSS 9.8): insecure deserialization in the SharePoint Tap MulticastTransceiver component lets a remote, unauthenticated attacker run arbitrary code.
  • CVE-2026-87977 (9.8): unauthenticated SQL injection in the edge-controller component; CVE-2026-82339 (9.1): the SharePoint S-TAP RelayService has no authentication, so attackers can forge audit events and read the monitoring policy.
  • The bulletin fixes 11 more flaws, including local privilege escalation via the SUID podman_wrapper binary (CVE-2026-84087) and five bugs in the bundled undici library.
  • Fix: version 12.2.4. IBM lists no workaround.

Vulnerabilities: CVE-2026-84236, CVE-2026-87977, CVE-2026-82339

What happened

On 19 November 2026 IBM published a security bulletin for IBM Guardium Data Protection 12.2 listing fourteen vulnerabilities. Three carry critical scores and can be exploited over the network without logging in. The CVE records appeared in NVD the same day. Version 12.2.4 fixes them.

CVE CVSS 3.1 Weakness Impact according to IBM
CVE-2026-84236 9.8 deserialization of untrusted data (CWE-502) unauthenticated code execution
CVE-2026-87977 9.8 SQL injection (CWE-89) reading and modifying sensitive database data
CVE-2026-82339 9.1 missing authentication (CWE-306) forged audit events, access to the monitoring policy

Technical details

  • CVE-2026-84236 sits in the SharePoint Tap MulticastTransceiver component, which receives data from SharePoint monitoring. It deserializes untrusted data without validation, so a remote attacker can execute arbitrary code.
  • CVE-2026-87977 is a SQL injection in the edge-controller component. An attacker without an account can read or change sensitive information in the database.
  • CVE-2026-82339: the SharePoint S-TAP RelayService does not require authentication. An attacker can inject fake audit events and read the active monitoring policy – in other words, learn what is being watched.

All three have the vector AV:N/AC:L/PR:N/UI:N: network attack, no account, no user interaction. IBM has published no further details or proof-of-concept code.

Why it matters: Guardium sits in the middle of an organisation's most sensitive data. S-TAP agents run directly on database servers and stream query records to the collector. Whoever controls the collector sees who touches the data and how – and can influence what ends up in the audit trail. Code execution combined with the ability to forge audit records is therefore worse than the scores alone suggest.

Other fixes in the same bulletin:

CVE CVSS 3.1 What it allows, according to IBM
CVE-2026-84273 8.1 an authenticated attacker deleting arbitrary files on the appliance (path traversal in datasources)
CVE-2026-82342 8.1 a stack buffer overflow when parsing a PROXY protocol v1 header – a crash or possibly code execution
CVE-2026-85018 8.1 credential interception by a man-in-the-middle (the Terraform provider does not validate TLS certificates)
CVE-2026-84087 7.8 local privilege escalation to root via the SUID podman_wrapper binary on the collector
CVE-2026-84065 6.5 an out-of-bounds read – information leak or crash
CVE-2026-84211 5.9 forged audit records due to improper neutralisation of log output

The remaining five (CVE-2026-13697, -14643, -15157, -16728, -16729) are in the bundled undici library for Node.js and concern shared caching, headers and cookies. IBM does not say which undici version ships with Guardium 12.2.4.

Who is affected

IBM Guardium Data Protection 12.2 on Linux before 12.2.4. The bulletin lists no other product branches as affected. Deployments where collector services and S-TAP ingestion are reachable from large parts of the corporate network are most exposed. If a service provider runs Guardium for you, ask them about the update status.

How to tell if you were compromised

IBM has not published indicators of compromise. At a minimum, check for:

  • unexpected processes and outbound connections on Guardium appliances,
  • changes to monitoring policies and accounts that you did not make,
  • SharePoint S-TAP audit events from unknown sources. Until you patch, treat those records with caution, because they could have been forged.

You can pull suspicious addresses out of your logs with our IOC extractor.

What to do

  1. Deploy Guardium Data Protection 12.2.4 (listed in Fix Central as SqlGuard_12.0p7240_GPU_Oct_2026_V12.2.4_FC).
  2. Restrict network access to Guardium appliances to the servers running S-TAP agents and the management network. IBM lists no workaround; this is general hardening.
  3. After upgrading, confirm the version on every appliance (central manager, aggregator, collector) and review accounts and policies.
  4. If you use the Guardium Terraform provider, rotate the credentials it handled after upgrading – they may have been intercepted (CVE-2026-85018).
  5. Prioritise appliances that receive SharePoint S-TAP data and are reachable from large parts of the network, then the rest.

Score the severity for your own environment with our CVSS calculator.

Timeline

  • 19 Nov 2026 – IBM publishes the bulletin and version 12.2.4; the CVE records go live in NVD (status "Awaiting Analysis").
  • 19 Nov 2026 – the flaws are not in CISA KEV and IBM reports no exploitation.

FAQ

What is Guardium Data Protection?

IBM's platform for monitoring access to databases and other data stores. S-TAP agents send activity records to an appliance (collector), which analyses them and stores them as an audit trail. Many organisations run it for compliance.

Why do forged audit records matter?

For many organisations Guardium is the evidence of who did what with sensitive data. An attacker who can inject fake events (CVE-2026-82339, CVE-2026-84211) can hide real activity or send investigators down false trails.

Are the flaws being exploited?

As of 19 November 2026 IBM reports no exploitation and the flaws are not in the CISA KEV catalog. IBM has published no technical details or proof-of-concept code.

Sources

  1. IBM – Security Bulletin: IBM Guardium Data Protection is affected by multiple vulnerabilities (19 Nov 2026)
  2. NVD – CVE-2026-84236
  3. NVD – CVE-2026-87977
  4. NVD – CVE-2026-82339

Spotted a mistake? Let us know and we will correct it openly.