Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach edge-controller gRPC service
-
DeliverySend malformed task data
-
ExploitTrigger unchecked type assertion
-
ExecutionCrash edge-controller process
-
ImpactDenial of service of monitoring
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to the Guardium Data Protection edge-controller gRPC service (the specific exposed component), against which an unauthenticated attacker sends malformed task data to trigger the unchecked type assertion. The CVSS vector (PR:N/UI:N/AC:L) confirms no authentication, no user interaction, and no special timing are needed once the gRPC endpoint is reachable. The primary limiting factor is reachability: the edge-controller gRPC port must be accessible to the attacker, so deployments that restrict this service to isolated internal management networks are not exposed to arbitrary remote attackers. Impact is limited to availability (process termination); no data disclosure or modification occurs. |
| Impact | This is a genuine but bounded-impact availability issue. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) is internally consistent with the description: a remote, unauthenticated, low-complexity attack with no user interaction, impacting only availability (C:N/I:N) via CWE-400 resource exhaustion/crash. There is no EPSS score, no CISA KEV listing, and no public exploit code provided in the input, so exploitation status is 'no public exploit identified at time of analysis' - this is not currently a confirmed-exploited emergency. The 7.5 rating is driven entirely by the A:H availability impact; because there is zero confidentiality or integrity impact, this is a lower real-world priority than a 7.5 with data exposure would be. The practical risk hinges on network exposure of the edge-controller gRPC service: if that port is reachable only from trusted internal management networks (typical for Guardium deployments), real-world risk is substantially lower than the 'network' vector implies. A vendor patch is available, which is the clear remediation signal. No signals conflict; the main uncertainty is the actual network reachability of the gRPC service in production, which defenders must verify locally. |
| Exploit ScenarioDerived | An attacker with network reachability to the IBM Guardium edge-controller gRPC service sends a crafted task message containing malformed data that violates an expected type. The unchecked type assertion in the edge-controller fails, causing the process to crash and halting data-protection monitoring until the service restarts. No public proof-of-concept is identified at time of analysis, and the low attack complexity (AC:L) means no special timing or conditions are needed once the service is reachable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Denial of service in IBM Guardium Data Protection 12.2.2 allows an unauthenticated remote attacker with network reachability to the edge-controller gRPC service to terminate the edge-controller process by supplying malformed task data that trips an unchecked type assertion. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms no authentication, no user interaction, and no special timing are required once the port is exposed, and impact is confined to availability - the process crashes unexpectedly with no data disclosure or modification. There is no public exploit identified at time of analysis and no confirmed active exploitation (the CVE is not in CISA KEV), so the practical exposure is governed by reachability: deployments that keep the edge-controller gRPC endpoint on isolated management networks are not exposed to arbitrary remote attackers, while internet- or broad-LAN-accessible instances are at meaningful disruption risk. The primary limiting factor is that the gRPC port must be reachable, making this a genuine but bounded-impact availability issue.
RemediationAI
Patch availability is per the vendor advisory: apply the fix for Guardium Data Protection 12.2.2 published by IBM at https://www.ibm.com/support/pages/node/7288627, and confirm the fixed build identifier with IBM support or the advisory itself, since no exact fix version number is specified in the available data. Until the patch is applied, the most effective control is reducing reachability of the edge-controller gRPC port: restrict it with firewall rules, security groups, or ACLs so only known Guardium management hosts and trusted collector networks can connect, and never expose it to the internet or to general user VLANs - the trade-off is that remote or distributed data sources outside the trusted zone will fail to register until their hosts are added to the allowlist. Where the edge-controller function is not in active use, stop or disable the service entirely, accepting loss of edge data-source connectivity. Because the failure mode is a crash, configuring process supervision or automatic restart reduces outage duration, but this is a stopgap only, as an attacker can repeatedly re-trigger the termination and each restart still causes a service interruption and loss of in-flight tasks. Monitoring edge-controller process restarts and alerting on unexpected termination can provide early warning of attempted exploitation; note that these compensating controls reduce but do not eliminate the risk, and none of them address the underlying unchecked type assertion the way the vendor patch does.
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 affected component is the edge-controller shipped with IBM Guardium Data Protection, a management-plane service that communicates with remote data sources and edge/collector endpoints over a gRPC interface. The root cause is an unchecked type assertion applied to task data received from a gRPC caller: when the incoming payload does not match the concrete type the handler expects, the assertion fails and the Go runtime panics, taking down the edge-controller process. The CVE is categorized under CWE-400 (Uncontrolled Resource Consumption) as a resource-exhaustion/availability class; functionally the defect is a failure to validate attacker-controlled input types before asserting them (closer to improper type handling), but the observable outcome is process termination rather than memory or CPU exhaustion. The CPE record cpe:2.3:a:ibm:guardium_data_protection:*:*:*:*:*:*:*:* uses a wildcard version, so the CPE alone does not pin the affected release; the description and vendor advisory identify 12.2.2 as affected, and organizations running that release line should confirm exposure against IBM's advisory. The gRPC service is unauthenticated in the attack path described (PR:N in both the provided and independently assessed vector), meaning any host able to open a TCP connection to the edge-controller port can deliver the malformed task payload.
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:N/UI:N/S:U/C:N/I:N/A:H
Unauthenticated remote gRPC input with no user interaction gives AV:N/AC:L/PR:N/UI:N; the flaw only crashes the process, so C:N/I:N/A:H.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM Guardium Data Protection 12.2.2 is affected by a denial-of-service vulnerability in the edge-controller. An unauthenticated remote attacker with network access to the edge-controller gRPC service can provide malformed task data that triggers an unchecked type assertion, causing the edge-controller process to terminate unexpectedly.
Executive ViewAI
IBM Guardium Data Protection 12.2.2, the platform many organizations rely on to monitor and audit database activity for compliance, contains a remotely triggerable crash in its edge-controller service that any unauthenticated attacker who can reach that network port can use to take the component offline. Because Guardium is typically a control that supports regulatory and internal audit obligations, repeated outages could create monitoring blind spots and disrupt evidence collection rather than expose or alter data. Leadership should care primarily about which instances are reachable outside trusted management networks, since that exposure determines whether this is a contained operational nuisance or a live availability risk to a compliance-critical system.
Apply vendor patch.
Threat Intelligence Overview
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Guardium Data Protection
View allAuthenticated command injection in IBM Guardium Data Protection 12.2 allows a user who can reach the GIM (Guardium Insta
SQL 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
EUVD-2026-95168
GHSA-g3c4-g93w-p4xg
NVD
CVE.org
EPSS
VulDB
Exploit-DB