Cyber & AI intelligence
Briefs indexed3958
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-84236 2026-11-20

IBM Guardium Data Protection 12.2 Flaw Allows Unauthenticated Remote Code Execution (CVE-2026-84236)

"CVE-2026-84236 is a critical (CVSS 9.8) insecure deserialization flaw in IBM Guardium Data Protection 12.2 that an unauthenticated remote attacker could use to run arbitrary code on an affected system."

CVE-2026-84236 is a critical (CVSS 9.8) insecure deserialization flaw in IBM Guardium Data Protection 12.2 that an unauthenticated remote attacker could use to run arbitrary code on an affected system.

What Is It

IBM reports that Guardium Data Protection 12.2 has an insecure deserialization flaw (CWE-502) in its SharePoint Tap MulticastTransceiver component. According to the NVD description, an unauthenticated remote attacker could exploit it to execute arbitrary code on the affected system.

IBM's PSIRT published the CVE on 2026-11-19. NVD lists the record as "Awaiting Analysis," so NVD has not yet published its own assessment.

Why It Matters

IBM's CVSS 3.1 score is 9.8 (Critical), with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms:

CISA's SSVC assessment in the NVD record rates the flaw as automatable with a total technical impact. That makes it a strong candidate for mass exploitation once a working exploit exists.

Exploitation status: this CVE is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. CISA's SSVC assessment in the NVD record records exploitation as "none." Active exploitation has not been confirmed so far.

What's Vulnerable

The supplied data lists no other versions as affected.

Patch Status

IBM has published a security bulletin for this flaw (linked below). The supplied NVD data does not name a fixed version or specific remediation steps, and there is no KEV entry, so there is no CISA-mandated required action or due date. Administrators running Guardium Data Protection 12.2 should follow the remediation guidance in the IBM bulletin. Because the flaw needs no authentication and can be automated, treat it as a priority even though no exploitation has been reported.

Sources