Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach QRadar network service
-
DeliverySend crafted resource-intensive requests
-
ExploitTrigger uncontrolled resource consumption
-
ExecutionExhaust CPU/memory/connections
-
ImpactDeny SIEM availability to defenders
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 | The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication or user interaction is required: a remote attacker needs only network reachability to an exposed IBM QRadar SIEM service to attempt exploitation. The description does not name a specific feature, protocol, port, or non-default configuration as a precondition, so the limiting factors are primarily network exposure (QRadar consoles/collectors are often segmented on internal management networks rather than internet-facing) and the specific affected version range, which is not disclosed in the provided data and must be confirmed against IBM advisory node 7292244. Impact is limited to availability - no data disclosure or integrity loss - so successful exploitation disrupts SIEM monitoring but does not directly compromise data. |
| Impact | The IBM-provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H, base 8.6) describes a remotely reachable, low-complexity, unauthenticated denial-of-service with high availability impact and a scope change, which on paper is a serious signal for an always-on security appliance. However, the real-world risk signals are thin and partly uncorroborated: there is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the provided data, so there is no public exploit identified at time of analysis. The impact is confined to availability (C:N/I:N) - this is a crash/exhaustion issue, not data theft or code execution - which lowers its practical priority relative to its headline score. One notable tension is the S:C (scope changed) rating: for a self-contained resource-exhaustion DoS this is aggressive, since uncontrolled resource consumption (CWE-400) typically degrades only the affected QRadar component rather than a separately-authorized downstream system; verify the scope justification with IBM advisory node 7292244. Net assessment: a credible availability threat to internet- or network-reachable QRadar deployments that should be patched on a normal-to-expedited cycle, but not an emergency on the level of an actively-exploited RCE given the DoS-only impact and absence of any exploitation evidence. |
| Exploit ScenarioDerived | A remote attacker with network reach to the QRadar SIEM sends a stream of specially crafted or high-volume requests that trigger uncontrolled resource consumption (CPU, memory, or connection/thread exhaustion), degrading or crashing the service. Because no authentication or user interaction is required (PR:N/UI:N), any attacker able to reach the exposed service can attempt it. No public proof-of-concept is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Unauthenticated remote resource exhaustion in IBM QRadar SIEM allows a network-reachable attacker to degrade or take down the security monitoring platform without credentials or user interaction, per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, availability-only impact). The vendor scored the issue 8.6 with Scope:Changed, while our independent assessment treats scope as unchanged (7.5-equivalent), since no downstream component beyond the QRadar service itself is demonstrated; either way the practical effect is loss of SIEM visibility while the attack runs. No public exploit code or confirmed active exploitation was identified at time of analysis, and the affected version range is not disclosed in the supplied data - it must be confirmed against IBM advisory node 7292244 before exposure decisions are made.
RemediationAI
No vendor-released patch or exact fix version was identified in the provided data, so the first action is to retrieve IBM advisory node 7292244 (https://www.ibm.com/support/pages/node/7292244) to determine the affected version range and the specific fix level or interim fix IBM prescribes, then upgrade QRadar SIEM to that level. In the interim, reduce exposure by firewalling QRadar management, REST API, and event-ingestion listeners so only known collector and administrator subnets can reach them - this is the highest-value control here because the vector requires only network reachability, but it will break remote collectors, off-net admin access, and third-party integrations that are not explicitly allowed. Where feasible, disable or ACL unused ingestion protocols and listener ports; the trade-off is loss of log coverage from any source still using them. Front QRadar API endpoints with a reverse proxy or load balancer enforcing per-source connection and request-rate limits, accepting added latency and the risk of throttling legitimate high-volume API clients. Instrument console, event processor, and collector CPU, memory, connection counts, and event-queue depth so resource-exhaustion attempts are detected early, and pre-plan failover or collector rebalancing so monitoring gaps during an attack are minimized. Because the issue is availability-only, no credential or data-integrity remediation is required, but verify no unauthorized configuration changes were made during any observed outage.
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 root cause class is CWE-400, Uncontrolled Resource Consumption: some network-facing QRadar SIEM service allocates or holds a resource (memory, threads/connection state, queue slots, or processing time) in proportion to attacker-supplied input without an effective cap, so repeated requests exhaust it and starve legitimate operations. QRadar is a distributed SIEM whose console, event processors, and collectors expose numerous listeners - event ingestion (syslog/TLS syslog), the REST API, and administrative interfaces - and any one of these being the affected surface would be reachable from wherever QRadar accepts telemetry or API calls. Notably, the vendor vector asserts Scope:Changed (S:C), implying the resource exhaustion can spill into another security authority, whereas our assessment uses S:U because the supplied description and references do not document cross-component impact; we therefore treat blast radius as confined to the QRadar service and its dependent monitoring pipeline. No CPE data or CWE-400 sub-class detail was provided, and the advisory does not identify the specific protocol, port, or non-default configuration involved, so the exact vulnerable component cannot be pinned down from the available intelligence.
Know when the next one hits your stack
- 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:C/C:N/I:N/A:H
Remote unauthenticated low-complexity DoS gives AV:N/AC:L/PR:N/UI:N and A:H with no C/I impact; assessed S:U as a self-contained resource-exhaustion crash, unlike IBM's S:C.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
IBM QRadar SIEM could allow a remote attacker to cause a denial of service due to uncontrolled resource consumption.
Executive ViewAI
The IBM QRadar SIEM platform is exposed to an unauthenticated availability flaw that can interrupt security monitoring and create visibility gaps for the teams that depend on it. Because no credentials or user action are required and a vendor patch is not yet available, leadership should prioritize confirming exposure and containing network reachability, especially for broadly accessible or internet-facing QRadar deployments.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting network access to IBM QRadar SIEM management and data interfaces to trusted networks, applying rate limiting and traffic filtering at perimeter controls, monitoring resource utilization and availability for signs of exhaustion, maintaining failover capacity and incident response playbooks for SIEM outage, and confirming affected versions via IBM advisory node 7292244 while escalating with IBM for patch and mitigation guidance.
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.
EUVD-2026-106860
GHSA-f3c3-ppjc-gwr4
NVD
CVE.org
EPSS
Exploit-DB