On this page (7 sections)

A critical vulnerability, CVE-2026-82339, affects the SharePoint S-TAP RelayService in IBM Guardium Data Protection 12.2. According to the GitHub Advisory Database, the service does not authenticate callers, so an unauthenticated attacker on the network can inject forged audit events and read the active monitoring policy.

If you run Guardium to audit database or SharePoint activity, this matters twice: the data you rely on for investigations can be polluted, and an attacker can learn what you are watching for. At the time of writing, the public record is thin, so this article separates what is confirmed from what is not.

What happened

The vulnerability was published on November 19, 2026 through the National Vulnerability Database and mirrored to the GitHub Advisory Database. The description says IBM Guardium Data Protection 12.2 is vulnerable to missing authentication in the SharePoint S-TAP RelayService. IBM's own page for the issue is IBM support node 7297484, which is the place to look for the vendor's official fix guidance.

Only one independent publisher covers this so far. The NVD entry repeats the same description, so it is not separate confirmation. The GitHub advisory is marked unreviewed, and it lists affected and patched versions as unknown.

Technical details

CWE-306 describes a product that performs no authentication for functionality that needs a provable identity. In plain terms, the RelayService accepts requests without asking who is sending them. Any host that can reach the service over the network can talk to it as if it were a trusted component.

The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. That reads as: reachable over the network, low complexity, no privileges, no user interaction, unchanged scope, high impact on confidentiality and integrity, and no impact on availability. The 9.1 score fits that profile.

The two stated consequences map to those impacts:

  • Integrity: forged audit events can be injected. An attacker could add misleading records, or bury real activity in noise, which weakens the audit trail.
  • Confidentiality: the active monitoring policy can be accessed. Knowing what is and is not monitored helps an attacker plan activity that avoids detection.
The sources do not describe the request format, ports, or a proof of concept, and no exploit details are given here. The research does not say whether the flaw allows changing the policy, only accessing it.

Who is affected

The stated affected product is IBM Guardium Data Protection 12.2, specifically the SharePoint S-TAP RelayService. Deployments that do not use the SharePoint S-TAP are less likely to expose this component, but the sources do not say how it is enabled, so confirm this in your own environment rather than assuming.

Exposure depends mostly on network reachability. Because no authentication is required, any system that can connect to the relay service, including a compromised internal host, is a potential source of forged events. Flat internal networks carry the most risk.

How to check your exposure

  1. Confirm your Guardium version. If you are not on 12.2, the advisory as written does not name your version, but check IBM's page for other affected releases.
  2. Find out whether the SharePoint S-TAP is deployed and which hosts run the RelayService.
  3. Identify which networks and hosts can reach that service, including jump hosts, VPN ranges and other server segments.
  4. Read the IBM support page for the official affected-version list and fix or workaround guidance.

On a Linux host you administer, this read-only command lists listening TCP sockets so you can see which ports a service is bound to and on which addresses. Run it as a user allowed to see process names, and look for the relay service on an address wider than it needs:

List listening TCP sockets and owning processes (Linux)Shell
ss -tlnp
The research does not give the service name, port or host operating system for the RelayService, so this command is a general way to review listeners, not a confirmed check for this flaw. Use IBM's documentation to identify the right service.

What to do now

  1. Open IBM's page at https://www.ibm.com/support/pages/node/7297484 and follow its fix or mitigation instructions for Guardium Data Protection 12.2.
  2. Apply the vendor fix as soon as IBM provides one for your deployment, after testing in a non-production environment.
  3. Until patched, restrict network access to the SharePoint S-TAP RelayService to only the hosts that legitimately need it, using firewall rules or segmentation.
  4. Do not expose the relay service to the internet or to untrusted network segments.
  5. Review recent audit data for events that look out of place: unknown sources, odd timestamps, or records for activity that did not occur.
  6. Treat the current monitoring policy as potentially known to an attacker and consider whether sensitive rules need review.
  7. Record the Guardium version and S-TAP inventory so you can verify the fix later.
Caution. Changing firewall rules or restarting Guardium components can interrupt auditing. Plan the change, confirm that legitimate S-TAP traffic still flows afterward, and avoid leaving a gap in audit coverage.

Detection and monitoring

There are no published indicators of compromise in the sources. Detection therefore rests on behavior: watch for connections to the relay service from hosts that are not part of your S-TAP deployment, and for audit events whose origin or content does not match known activity.

  • Log and alert on new source addresses connecting to the RelayService port.
  • Compare event volumes against your normal baseline; a sudden burst of events from one source deserves a look.
  • Keep a copy of your monitoring policy under change control so unexpected differences stand out.
  • Re-check IBM's page and the NVD record regularly, since affected and fixed versions are still listed as unknown in the GitHub entry.

For the web-facing side of your estate, a read-only scan and certificate and DNS monitoring help you notice unexpected changes, though they cannot see inside an internal audit service like this one. For broader guidance, see our small business website security guide.

Timeline

Summary
DateEvent
2026-11-19CVE-2026-82339 published by NVD and added to the GitHub Advisory Database
2026-11-19GitHub advisory last updated; affected and patched versions listed as unknown

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-82339 - GitHub Advisory Databasegithub.com
  2. CVE-2026-82339: IBM Guardium Data Protection 12.2 is vulnerable to missing authentication in the SharePoint S-TAP RelayService, allowing an unauthenticated network attacker…nvd.nist.gov ·
  • IBM Guardium
  • CVE-2026-82339
  • CWE-306
  • S-TAP
  • database auditing