IBM Guardium Data Protection missing authentication in SharePoint S-TAP RelayService
Affects IBM Guardium Data Protection 12.2 through the SharePoint S-TAP RelayService component. Fixed in 12.2.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 12.2.4
- Who is exposed
- Not reported
Summary
IBM Guardium Data Protection has a missing authentication flaw in its SharePoint S-TAP RelayService. An attacker can reach it remotely over the network without logging in, then inject forged audit events and view the active monitoring policy.
Written by a model
Original description
IBM Guardium Data Protection 12.2 is vulnerable to missing authentication in the SharePoint S-TAP RelayService, allowing an unauthenticated network attacker to inject forged audit events and access the active monitoring policy.
Who should check
Teams running IBM Guardium Data Protection 12.2 with the SharePoint S-TAP RelayService, such as Guardium appliance operators monitoring SharePoint.
“IBM Guardium Data Protection 12.2”
What to do
Upgrade to a fixed version: 12.2.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-82339 (IBM Guardium Data Protection Missing Authentication), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-82339 (entry last updated 2026-11-19):
Affected:
- IBM Guardium Data Protection: versions 12.2
Fixed versions: 12.2.4.
Conditions (all must be true for the bug to be hit):
- Affects IBM Guardium Data Protection 12.2. (source: https://www.ibm.com/support/pages/node/7297484)
- The flaw is in the SharePoint S-TAP RelayService component. (source: https://www.ibm.com/support/pages/node/7297484)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-82339 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82339 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.ibm.com/support/pages/node/7297484
- https://www.cve.org/CVERecord?id=CVE-2026-82339
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-82339
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-82339"}.Affected versions
- IBM Guardium Data Protection12.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now1 day
- Posted on X by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Patch | ibm.com · support/pages/node/7297484 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-82339 |
| Record | NVD · CVE-2026-82339 |
Questions about CVE-2026-82339
Is CVE-2026-82339 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Which versions are affected by CVE-2026-82339?
Guardium Data Protection: version 12.2.
Source: cve.now feed data
Am I affected, and how do I check?
Related
- CVE-2026-84236IBM Guardium Data Protection Deserialization of Untrusted Data
- CVE-2026-87977IBM Guardium Data Protection SQL Injection
- CVE-2026-75875Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection
- CVE-2026-80381Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection
- CVE-2026-81932Multiple vulnerabilities affect the Sniffer component as part of IBM Guardium Data Protection
- CVE-2026-82342IBM Guardium Data Protection Buffer Overflow
No corrections so far. Something wrong on this page? Report an error.