CVE-2026-82335: IBM Guardium Data Protection Buffer Overflow

Published Oct 8, 2026
·
Updated

IBM Guardium Data Protection 12.0, 12.1, 12.2 is vulnerable to a heap-based buffer overflow in the MongoDB protocol parser. A remote attacker could send a specially crafted MongoDB SCRAM username containing an excessive length and cause memory corruption, potentially resulting in denial of service or arbitrary code execution.

Other sources

IBM Security Guardium is vulnerable to a heap-based buffer overflow in the MongoDB protocol parser. A remote attacker could send a specially crafted MongoDB SCRAM username containing an excessive length and cause memory corruption, potentially resulting in denial of service or arbitrary code execution.

— IBM

Affected Software

5 affected components
IBM Guardium Data Protection=12.0, =12.1, =12.2
IBM Guardium Data Protection<=12.2, 12.1, 12.0
IBM Guardium Data Protection=12.0
IBM Guardium Data Protection=12.1
IBM Guardium Data Protection=12.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade IBM Guardium Data Protection Sniffer to a version that resolves this vulnerability.

    Patch SqlGuard_12.0p4018_SnifferUpdate

Event History

Oct 8, 2026
CVE Published
via IBM·12:00 AM
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
CVE Published
via MITRE·07:12 PM
Data Sourced
via MITRE·07:12 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are affected?

IBM Guardium Data Protection versions 12.0, 12.1, and 12.2 are identified as vulnerable. The issue is in the MongoDB protocol parser.

2

What does an attacker need to exploit this issue?

A remote attacker can attempt exploitation by sending a specially crafted MongoDB SCRAM username with an excessive length. No privileges or user interaction are required, although the listed attack complexity is high.

3

What could successful exploitation cause?

The excessive-length username can trigger heap memory corruption. This could result in denial of service or potentially arbitrary code execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203