On this page (7 sections)

A critical SQL injection flaw, tracked as CVE-2026-87977, has been published for IBM Guardium Data Protection 12.2. According to the GitHub Advisory Database entry, the problem sits in the edge-controller component and can be reached by an unauthenticated remote attacker, who could access or modify sensitive database information.

If your organization runs Guardium to monitor database activity, this is worth a same-day look. The product is often deployed to protect the most sensitive data you hold, so a flaw in it deserves priority even while details are still sparse.

What is confirmed so far

The public record is short. The NVD entry and the GitHub advisory carry the same one-sentence description: IBM Guardium Data Protection 12.2 is vulnerable to SQL injection in the edge-controller component, and an unauthenticated remote attacker could use it to access or modify sensitive database information. The NVD record repeats that text, so the two should not be counted as independent confirmation.

The advisory points to an IBM support page, IBM node 7297484, as a reference. The text of that page was not available to us, so we cannot say which fix, interim fix or workaround IBM recommends. Treat that page as the authoritative source for remediation.

Unknown at the time of writing: the exact range of affected builds beyond 12.2, the fixed version, whether any workaround exists, and whether the flaw is being exploited. The GitHub entry is marked unreviewed and lists affected and patched versions as unknown.

What the weakness is

The flaw is classified as CWE-89, improper neutralization of special elements used in an SQL command. In plain terms, the application builds a database query using input that an outside party can influence, and it fails to separate data from query syntax. An attacker can then make the database interpret their input as part of the command.

The CVSS vector shows why the score is 9.8. The attack vector is the network, complexity is low, no privileges and no user interaction are required, and the impact on confidentiality, integrity and availability is rated high. That combination means no login and no tricking of an administrator is needed, only network reachability of the vulnerable component.

Who is realistically exposed

  • Organizations running IBM Guardium Data Protection 12.2, in particular where the edge-controller component is enabled or reachable over the network.
  • Environments where Guardium management or collector interfaces are reachable from broad internal networks, partner links or the internet. The sources do not say how the edge-controller is normally exposed, so verify this in your own deployment.
  • Teams that rely on Guardium to audit access to regulated data, since tampering with its database could affect both the data and the audit trail. This is a reasonable concern based on the description of data modification, not a reported incident.

If you do not run Guardium 12.2, this specific CVE does not apply to you based on the published description. Other versions are not confirmed safe either, because the sources do not list the full affected range.

How to check your exposure

  1. Identify every Guardium Data Protection appliance and collector in your inventory and record its product version.
  2. Confirm whether any run version 12.2, and whether the edge-controller component is in use.
  3. Map which networks can reach those systems. Note any path from the internet, partner networks or untrusted internal segments.
  4. Open the IBM support page referenced by the advisory and compare its affected and fixed versions with your inventory.

Review your logs around the same time. The commands below are generic examples for a web or reverse proxy log; adjust the path to your environment. They only read data and look for requests to the edge-controller, not for a confirmed attack signature, since none is published.

Search a reverse proxy access log for requests mentioning edge-controller (read-only; adjust the…Shell
grep -i "edge-controller" /var/log/nginx/access.log | tail -n 100

Look for unexpected sources, unusual volume, or error responses clustered around that path. A hit is not proof of compromise, and no hit does not prove safety, because requests may not pass through that proxy.

What to do now

  1. Read the IBM support page for this CVE (node 7297484) and follow IBM's remediation guidance as soon as it names a fix.
  2. Apply the IBM-provided update or interim fix to every Guardium 12.2 system, starting with those reachable from less trusted networks.
  3. Until you can patch, restrict network access to Guardium services, including the edge-controller, to the smallest set of administrative and collector hosts using firewall rules or ACLs.
  4. Make sure Guardium management interfaces are not exposed to the internet.
  5. Review Guardium and surrounding network logs for unusual requests to the edge-controller and for unexpected changes to configuration or data.
  6. Take a backup or snapshot of the appliance configuration before patching, following IBM's documented procedure.
  7. If you find signs of tampering, rotate credentials used by Guardium and treat the system as potentially compromised while you investigate.
Caution. Patching an appliance usually involves a restart or maintenance window and can interrupt database activity monitoring. Schedule it, back up first, and follow IBM's official instructions rather than improvised steps.

Detection and monitoring afterwards

Because exploitation status is unknown, keep watching rather than assuming the issue is closed. Check the IBM page and the GitHub advisory for updates to affected and patched versions, and check whether the CVE is later added to the CISA Known Exploited Vulnerabilities catalog.

  • Alert on new or unusual connections to Guardium hosts from outside your admin ranges.
  • Watch for database errors or unexpected query patterns on the Guardium backend.
  • Track configuration changes and new accounts on the appliance.

For public-facing systems you run alongside Guardium, a free SSL certificate check and certificate and DNS monitoring can help you notice unexpected changes. They do not detect this vulnerability. For background on the bug class, see our guide on what a WAF is, which covers one layer that can reduce SQL injection risk on web applications, though it is no substitute for IBM's fix.

Timeline

Known dates from the sources
DateEvent
Nov 19, 2026CVE-2026-87977 published by the National Vulnerability Database
Nov 19, 2026Advisory GHSA-jf9v-v4vr-2q9p published and last updated in the GitHub Advisory Database (marked unreviewed)

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-87977 - GitHub Advisory Databasegithub.com
  2. CVE-2026-87977: IBM Guardium Data Protection 12.2 is vulnerable to SQL injection in the edge-controller component.nvd.nist.gov ·
  • IBM Guardium
  • SQL injection
  • CVE-2026-87977
  • CWE-89
  • critical vulnerability