EUVD-2026-87097
GHSA-6h2g-mwcf-v922
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privileged Guardium account
-
DeliveryUpload crafted GIM bundle
-
ExploitInject arguments into tar command during import
-
ExecutionExecute arbitrary commands with elevated privileges
-
ImpactCompromise Central Manager
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account (PR:L) on the IBM Guardium Data Protection 12.2 Central Manager with access to the GIM bundle import functionality. The attacker must be able to supply a crafted GIM bundle whose contents cause attacker-controlled arguments to be passed to the tar command during import. Limiting factors: valid low-privileged authentication is mandatory (not exploitable pre-auth), the specific vulnerable version is 12.2, and the attack targets the GIM import feature specifically rather than any default network service; no user interaction by a victim is needed. |
| Impact | The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) indicates a network-reachable, low-complexity command-injection flaw requiring only low-level authentication and no user interaction, yielding full RCE with elevated privileges on the Guardium Central Manager. This is a genuinely serious technical impact (CWE-78, triple-H impact on a security-management appliance). However, exploitation-likelihood signals are absent: no EPSS score is provided, the CVE is NOT on CISA KEV, and no public POC is referenced - only a vendor patch node. So while the *impact* justifies prioritizing patching, there is no evidence of active or imminent exploitation. The PR:L requirement is a meaningful gate: an attacker must first hold a valid, if low-privileged, account on the Guardium environment, which narrows the realistic threat to insiders or attackers who have already gained a foothold. Net: patch promptly given the RCE-on-security-infrastructure impact, but current real-world exploitation risk is unproven rather than confirmed-critical. |
| Exploit ScenarioDerived | An attacker with low-privileged authenticated access to the IBM Guardium Central Manager uploads a maliciously crafted GIM bundle whose contents inject attacker-controlled arguments into the underlying tar command invoked during import. When the bundle is processed, the injected arguments execute arbitrary OS commands with elevated privileges on the Central Manager. No public exploit code is identified at time of analysis, and exploitation requires prior authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Authenticated command injection in IBM Guardium Data Protection 12.2 allows a user who can reach the GIM (Guardium Installation Manager) bundle import functionality to supply a crafted bundle whose contents cause attacker-controlled arguments to be passed to the underlying tar command, resulting in arbitrary command execution with elevated privileges on the Central Manager. The flaw is network-reachable and requires only low-privileged authentication (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) with no victim user interaction, so any account able to trigger a bundle import should be considered capable of full compromise of the Central Manager. No public exploit code or confirmed active exploitation was identified at time of analysis; the vendor has published a fix advisory.
RemediationAI
Vendor patch is available per IBM's advisory at https://www.ibm.com/support/pages/node/7288035; the input data does not specify an exact fixed build string, so administrators should open that advisory and apply the indicated Guardium Data Protection 12.2 fix level (or the vendor-directed upgrade) to every Central Manager and any other node hosting the GIM import capability. Where the fix cannot be applied immediately, restrict the GIM bundle import function to a minimal set of fully trusted administrative accounts, since exploitation requires authenticated access to that workflow (PR:L) - removing or narrowing that permission blocks the attack path but may disrupt legitimate agent packaging and deployment operations. Enforce integrity and provenance checks on bundles before import (signed or checksum-verified bundles from a trusted build pipeline) and treat any unverified bundle as untrusted input; this reduces exposure but depends on the import path actually validating signatures, so it is not a substitute for the patch. Additional hardening includes monitoring Central Manager audit logs for unexpected tar invocations or child processes spawned from the import workflow, and reviewing accounts with GIM import rights for least privilege, with the trade-off that tightening these permissions can slow routine GIM agent rollout and maintenance. Note that restricting network reachability to the Central Manager's management interfaces limits who can attempt the attack but does not fix the underlying command injection.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic CWE-78 OS command injection arising from unsafe construction of a shell invocation. Guardium's GIM bundle import feature unpacks attacker-supplied bundle archives, and the import path passes bundle-derived values as arguments to the system tar utility without adequate sanitization or argument separation. Because the injected arguments are interpreted by the shell rather than treated as inert data, an attacker who controls the bundle contents can break out of the intended tar invocation and execute arbitrary commands in the context of the importing process. The affected component is the Guardium Central Manager, which orchestrates GIM agent deployment and updates across managed collectors and S-TAP hosts, giving the flaw a high-integrity and high-confidentiality impact on the Central Manager itself. CPE data (cpe:2.3:a:ibm:guardium_data_protection:*:*:*:*:*:*:*:*) is version-agnostic in the feed, but the vendor advisory and description scope the issue to the 12.2 release line. The CVSS vector's PR:L reflects that the attacker must already hold a valid Guardium account with permission to invoke the GIM import workflow; it is not pre-authentication exploitable, and the attack targets a specific administrative feature rather than a default listening service.
Know when Guardium Data Protection gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable management interface (AV:N), straightforward bundle crafting (AC:L), requires a low-privileged authenticated account (PR:L), no victim interaction (UI:N), and RCE yields full C/I/A on the appliance (S:U).
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM Guardium Data Protection 12.2 is affected by a command injection vulnerability in the GIM bundle import functionality. An authenticated attacker can provide a crafted GIM bundle that causes attacker-controlled arguments to be passed to the tar command, resulting in arbitrary command execution with elevated privileges on the Central Manager.
Technical POC Analysis
CWE-78, OS command injection / argument injection in the GIM (Guardium Installation Manager) bundle import functionality of IBM Guardium Data Protection 12.2.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
IBM Guardium Data Protection 12.2 has a high-severity issue in a management import function that could allow an authenticated low-privilege user to take control of the Central Manager. Because the Central Manager is central to data protection oversight and compliance, a compromise could disrupt sensitive data monitoring, regulatory reporting, and operational continuity. There is no public exploit identified at time of analysis, but a vendor fix is available, so leadership should prioritize controlled patching and access restrictions.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
More in Guardium Data Protection
View allSQL injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker to execute arbitrary SQL comma
Unauthenticated remote attackers can bypass security restrictions in IBM Guardium Data Protection 12.2 through the Chang
Missing authentication in the LoadBalancerServlet of IBM Guardium Data Protection 12.2 allows unauthenticated, network-r
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the app
Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2
Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based ac
Missing authentication on a critical management function in IBM Guardium Data Protection 12.2 and 12.2.2 allows unauthen
Missing authentication in the edge-controller component of IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthent
Unauthenticated SQL injection in IBM Guardium Data Protection 12.2 lets a remote attacker submit crafted input that is c
A heap-based buffer overflow in IBM Guardium Data Protection's S-TAP TrafficTap TDS login reassembly routine allows an u
Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL
Exploit-DB