IBM Guardium is an enterprise data-protection product used widely across organizations; an unauthenticated SQL injection enabling data theft/tampering is high-impact and newsworthy.
CVE-2026-81932
Unauthenticated SQL injection in IBM Guardium allows backend DB data access/modification.
Is CVE-2026-81932 being exploited?
Not confirmed. CVE-2026-81932 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-81932?
CVE-2026-81932 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-81932?
Not known from our data. No patch reference has been recorded for CVE-2026-81932, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-81932 affect?
CVE-2026-81932 affects IBM Guardium Data Protection 12.0, IBM Guardium Data Protection 12.1, IBM Guardium Data Protection 12.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-81932?
Apply vendor mitigations/patch ASAP; restrict access to Guardium, audit logs, and monitor for abuse.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated SQL injection lets attackers read, add, modify, or delete backend database records, enabling data theft and tampering.
Immediate action required
- affected12.0
- affected12.1
- affected12.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.