Skip to main content
Menu
CVEs

IBM Guardium Data Protection arbitrary file deletion in datasource functionality

CVE-2026-84273Published November 19, 2026, updated

8.1HighCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Specific setups only

Summary

IBM Guardium Data Protection has a path traversal flaw in its datasource functionality. An attacker with a low-privilege login can reach it over the network and use it to delete arbitrary files on the appliance.

Written by a model

Original description

IBM Guardium Data Protection 12.2 is vulnerable to path traversal in the datasource functionality. An authenticated attacker could exploit this vulnerability to delete arbitrary files on the appliance.

Who should check

Teams running IBM Guardium Data Protection 12.2 appliances, including those using the datasource functionality

“IBM Guardium Data Protection 12.2”

ibm.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects IBM Guardium Data Protection 12.2 The flaw is in the datasource functionality
  2. Apply the patch listed under Evidence.

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-84273 (IBM Guardium Data Protection Path Traversal), 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-84273 (entry last updated 2026-11-19):
Affected:
- IBM Guardium Data Protection: versions 12.2
Fixed versions: none listed yet.
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 datasource functionality (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, low-privilege login, no user action.
CISA KEV: CVE-2026-84273 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-84273 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
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-84273
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-84273"}.

Affected versions

cve.now Index

16Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.1/10CVSS 8.1
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Patchibm.com · support/pages/node/7297484
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-84273
RecordNVD · CVE-2026-84273

Questions about CVE-2026-84273

Is CVE-2026-84273 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?

The flaw is a path traversal in the datasource functionality of IBM Guardium Data Protection, and it can be used to delete arbitrary files on the appliance.

Source: ibm.com

Which versions are affected by CVE-2026-84273?

Guardium Data Protection: version 12.2.

Source: cve.now feed data

Am I affected, and how do I check?

The checked facts list IBM Guardium Data Protection 12.2 as affected. To check an installed version, compare it against 12.2 in the product's version information.

Source: ibm.com

How do I fix CVE-2026-84273?

The checked facts do not name a fixed version or patch, so no upgrade target can be given from them. Consult IBM's advisory for the remediation it provides.

Source: ibm.com

No corrections so far. Something wrong on this page? Report an error.