EUVD-2026-94971
GHSA-gw8w-wvff-h76m
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach GraphQL-enabled gateway endpoint
-
DeliverySend query with abusive fragment spreads
-
ExploitTrigger pathological memoization resolution
-
ExecutionExhaust CPU/memory resources
-
ImpactDenial of service for API consumers
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Asymmetric resource consumption control
|
| Exploitation Conditions | Exploitation requires the DataPower Gateway to be configured to accept and process GraphQL requests - the flaw lies in memoization of GraphQL fragment spreads, so a gateway not handling GraphQL is not exposed. Given AV:N/AC:L/PR:N/UI:N, no authentication, user interaction, or special timing is needed once a reachable GraphQL endpoint exists. The practical limiting factors are: (1) GraphQL proxying/processing must be enabled on the gateway, and (2) the attacker must have network reachability to that endpoint; impact is limited to availability (A:H) with no data exposure or modification. Affected releases are 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2. |
| Impact | This is a moderate-priority availability issue rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) indicates a remote, low-complexity, unauthenticated denial of service with no confidentiality or integrity impact - consistent with CWE-405 (asymmetric resource consumption) via improper memoization of GraphQL fragment spreads. No EPSS score, SSVC decision data, KEV listing, or POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The strongest mitigating factor not captured in the raw score is that exploitation requires the DataPower Gateway to be configured to process GraphQL traffic; the CVSS vector assumes this feature is in use. Net assessment: a credible, easy-to-trigger DoS for organizations that expose GraphQL through DataPower, but availability-only impact and the absence of exploitation signals place it below critical priority. Patch when feasible, prioritizing internet-facing GraphQL-enabled gateways. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted GraphQL query containing deeply or redundantly nested fragment spreads to a DataPower Gateway configured to process GraphQL. Improper memoization causes excessive CPU/memory consumption while resolving the fragments, degrading or halting service for legitimate API traffic. No public exploit code was identified at time of analysis, and low attack complexity (AC:L) means no special timing or race conditions are needed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Unauthenticated remote attackers can drive IBM DataPower Gateway into resource exhaustion and denial of service by sending crafted GraphQL queries that abuse improper memoization of fragment spreads. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, and per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H vector no authentication or user interaction is required once a reachable GraphQL-processing endpoint exists. Impact is confined to availability (no confidentiality or integrity loss), and there is no public exploit identified at time of analysis; exposure depends entirely on whether the gateway has been configured to accept and process GraphQL requests.
RemediationAI
IBM has released fixes for this issue; follow the vendor advisory at https://www.ibm.com/support/pages/node/7289775 to obtain and apply the appropriate DataPower Gateway firmware update for your release line (10.5.0, 10.6.0, 10.6CD, or 11.0.0) - patch status is 'Patch available per vendor advisory' and no specific fixed build number was provided in the source data, so confirm the exact target build from the IBM page before upgrading rather than assuming the latest maintenance level is sufficient. Where upgrading cannot be done immediately, the most effective compensating control is to stop exposing the vulnerable code path: disable or remove GraphQL processing/proxying on the DataPower service configuration for any endpoint that does not strictly require it, accepting the functional trade-off that legitimate GraphQL API consumers will break. If GraphQL must stay enabled, restrict network reachability to that listener using DataPower's own access-control/deny rules plus upstream firewall ACLs or a reverse proxy so only trusted client networks can reach it - this narrows but does not eliminate exposure from an allowed client. Enforce query-cost controls at the GraphQL layer (maximum query depth, fragment-spread limits, complexity/cost scoring, and response-size caps) and apply connection and request-rate throttling on the DataPower front end; these measures reduce amplification per request and slow an attack but are not a substitute for the vendor fix since they depend on tuning that may be bypassed. Monitor DataPower CPU, memory, and heap-pressure metrics for anomalous spikes correlated with GraphQL POST traffic so that an in-progress denial-of-service attempt can be detected and the offending client blocked.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 4 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw sits in DataPower's GraphQL request processing path, specifically in how the gateway memoizes (caches and reuses) the expansion of GraphQL fragment spreads. GraphQL fragments let a client define a reusable selection set and splice it into multiple places in a query via a spread; a correct implementation bounds or deduplicates repeated expansion so that a logically small query cannot balloon into an exponentially larger internal representation. Improper memoization means the gateway recomputes or re-expands shared fragments instead of reusing the cached result, so nested or repeated fragment spreads amplify CPU and memory consumption disproportionately to the size of the submitted document - the classic CWE-405 asymmetric resource consumption / amplification pattern. Because the attack rides on well-formed GraphQL over the same listener the gateway uses for normal API traffic, no malformed payload is required, and the CVSS vector confirms the weakness is reachable network-wide and unauthenticated. The underlying technology is IBM DataPower's API Gateway/GraphQL proxying feature set across the 10.5.0, 10.6.0, 10.6CD (10.6.1-10.6.6), and 11.0.0 firmware lines; a gateway that does not have GraphQL handling enabled never reaches the vulnerable code path.
Know when Datapower Gateway 10 6Cd 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
Remote unauthenticated attacker sends a crafted GraphQL query (AV:N, AC:L, PR:N, UI:N); only availability is affected (A:H), with no confidentiality or integrity impact and no scope change.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2 could allow a remote attacker to cause a denial of service due to improper memoization of GraphQL fragment spreads.
Executive ViewAI
IBM DataPower Gateway is exposed to an unauthenticated denial-of-service condition that can degrade or take the gateway offline wherever GraphQL request processing has been enabled. Because no credentials or user interaction are required, any reachable GraphQL endpoint represents a low-effort path to disrupting the API gateway that fronts critical internal and partner integrations. Leadership should care because the impact is availability-only but operationally significant: outages here cascade into dependent applications and customer-facing services, while confidentiality and integrity of data remain unaffected.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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 Datapower Gateway 10 6Cd
View allUnauthenticated remote code execution affects IBM DataPower Gateway across multiple release streams - 10.5.0.0 through 1
Unauthenticated remote code execution in IBM DataPower Gateway affects the 10.5.0.0 through 10.5.0.22, 10.6.0.0 through
Arbitrary code execution in IBM DataPower Gateway is possible when a user with existing local access to the appliance su
Empty-password LDAP authentication bypass in IBM DataPower Gateway lets remote, unauthenticated attackers obtain adminis
Remote code execution in IBM DataPower Gateway (10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0
A remotely reachable, unauthenticated out-of-bounds write (buffer overflow, CWE-787) in IBM DataPower Gateway can corrup
IBM DataPower Gateway versions 10.5.0.0-10.5.0.20, 10.6.0.0-10.6.0.8, and 10.6.1.0-10.6.5.0 are vulnerable to cross-site
Out-of-bounds write in IBM DataPower Gateway lets unauthenticated remote attackers corrupt process memory, resulting in
An out-of-bounds write in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through
XML external entity injection in IBM DataPower Gateway 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0
Heap-based buffer overflow (CWE-787) in IBM DataPower Gateway allows an unauthenticated remote attacker to crash the gat
Unauthenticated remote attackers can trigger a memory-safety fault in IBM DataPower Gateway that crashes the affected se
Exploit-DB