Overview 727 matches · 76 in Waratek scope · 7 protected · 11 exploited · 3 CISA KEV · 28 public PoC · 8 EPSS ≥ 0.5
727matches
76in Waratek scope10.5%
7protected1.0%
11exploited1.5%
3CISA KEV0.4%
28public PoC3.9%
8EPSS ≥ 0.51.1%
Protected by Waratek
7
1.0%
Rule in development
0
0.0%
Mitigation candidate
1
0.1%
No exploit published
68
9.4%
Outside Waratek scope
44
6.1%
Not applicable
607
83.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
7
1.0%
partly blocked
0
0.0%
not blocked
720
99.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 100 / year
19991
Not applicable1
Medium1
not blocked1
Working exploit published1
20000
20010
20020
20030
20040
20051
Not applicable1
Medium1
not blocked1
No public exploit1
20061
Not applicable1
Medium1
not blocked1
No public exploit1
20071
Not applicable1
Medium1
not blocked1
Working exploit published1
20083
Not applicable3
Medium3
not blocked3
No public exploit3
20095
Not applicable5
Medium5
not blocked5
No public exploit5
20106
Not applicable6
Medium6
not blocked6
Working exploit published5
No public exploit1
20115
Not applicable5
Medium5
not blocked5
No public exploit5
20121
Not applicable1
Medium1
not blocked1
No public exploit1
20134
Not applicable4
Medium4
not blocked4
Working exploit published1
No public exploit3
201417
No exploit published2
Not applicable15
Medium17
not blocked17
Exploited1
No public exploit16
201519
Protected by Waratek2
Not applicable17
Medium19
blocked by ARMR today2
not blocked17
Exploited1
Working exploit published2
No public exploit16
20168
Not applicable8
Medium8
not blocked8
No public exploit8
201740
No exploit published3
Not applicable37
Medium40
not blocked40
Working exploit published1
No public exploit39
201859
Protected by Waratek1
No exploit published4
Outside Waratek scope5
Not applicable49
Medium59
blocked by ARMR today1
not blocked58
Exploited1
Working exploit published1
No public exploit57
201989
Protected by Waratek1
No exploit published11
Outside Waratek scope8
Not applicable69
Medium89
blocked by ARMR today1
not blocked88
Exploited2
Working exploit published1
Proof of concept only1
No public exploit85
202052
No exploit published3
Outside Waratek scope3
Not applicable46
Medium52
not blocked52
Exploited2
No public exploit50
202157
Protected by Waratek2
Mitigation candidate1
No exploit published10
Outside Waratek scope10
Not applicable34
Medium57
blocked by ARMR today2
not blocked55
Exploited3
Working exploit published1
No public exploit53
202268
No exploit published7
Outside Waratek scope13
Not applicable48
Medium68
not blocked68
Working exploit published1
Proof of concept only2
No public exploit65
202362
Protected by Waratek1
No exploit published10
Not applicable51
Medium62
blocked by ARMR today1
not blocked61
Proof of concept only2
No public exploit60
202457
No exploit published7
Outside Waratek scope5
Not applicable45
Medium57
not blocked57
Exploited1
Proof of concept only2
No public exploit54
202571
No exploit published6
Not applicable65
Medium71
not blocked71
Working exploit published1
No public exploit70
2026100
No exploit published5
Not applicable95
Medium100
not blocked100
Proof of concept only2
No public exploit98
1999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-116376 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to conduct a phishing attack due to an open redirect vulnerability. |
| CVE-2026-110283 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to cause a denial of service due to improper validation of user-influenced resource identifiers. |
| CVE-2026-110282 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to bypass security restrictions due to improper access control. |
| CVE-2026-110281 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle technique. |
| CVE-2026-108910 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to obtain sensitive information due to missing required cryptographic step. |
| CVE-2026-108838 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a local attacker to cause a denial of service due to uncontrolled resource consumption. |
| CVE-2026-108767 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to conduct HTTP response splitting due to improper neutralization of HTTP headers. |
| CVE-2026-108588 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to bypass security restrictions due to a missing X-Content-Type-Options header allowing MIME type sniffing. |
| CVE-2026-108536 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to bypass security restrictions due to improper restriction of rendered UI layers or frames. |
| CVE-2026-105991 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to bypass security restrictions due to a missing Content Security Policy header. |
| CVE-2026-105702 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Db2 Genius Hub 1.1.2, 1.1.3, 1.1.4, 1.1.5 could allow a remote authenticated attacker to obtain sensitive information due to exposure of error messages containing internal implementation details. |
| CVE-2026-75063 | Medium | 2026-10-12 | Not applicable | No public exploit | IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary JavaScript due to improper output encoding. |
| CVE-2026-18541 | Medium | 2026-10-12 | Not applicable | No public exploit | IBM Planning Analytics 2.0, and 2.1 is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. |
| CVE-2026-106562 | Medium | 2026-10-07 | Not applicable | No public exploit | Backstage is an open framework for building developer portals. Prior to 2.1.6 in @backstage/plugin-search-backend and 1.8.7 in @backstage/plugin-search-backend-module-elasticsearch, search engine permission filtering could return documents denied by policy. An authenticated Backstage user subject to a DENY policy for search document types could receive unauthorized results in deployments with permission.enabled set to true and an Elasticsearch or OpenSearch backend. This issue is fixed in @backstage/plugin-search-backend 2.1.6 and @backstage/plugin-search-backend-module-elasticsearch 1.8.7. |
| CVE-2026-25270 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory corruption when processing command buffer requests with invalid length parameters in the Android Camera driver. |
| CVE-2026-25263 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory corruption while processing IOCTL command called from user space to the kernel with invalid parameters. |
| CVE-2026-103008 | Medium | 2026-10-06 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to Denial of Service via a specially crafted request that causes the server to construct and process a deeply nested data structure with no bound on recursion depth. Elasticsearch contains an uncontrolled recursion weakness in how it builds and serializes geometry values produced by scripted runtime fields. Unlike geometry supplied as text, which is subject to a nesting-depth limit, geometry constructed from a script's output is not bounded. An authenticated user with read access to a single index can submit a request defining such a field with a script that produces a deeply nested structure. Processing this request recurses past the available stack space, causing the affected node to terminate. The node does not recover automatically on all deployments and may require manual intervention to restore service. |
| CVE-2026-103006 | Medium | 2026-10-06 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to Denial of Service via a specially crafted, deeply nested request submitted to the aggregation feature of the search API. Elasticsearch contains an uncontrolled recursion weakness in its search aggregation processing. An authenticated user with read access to a single index can submit a specially crafted request containing deeply nested aggregation definitions. Processing this request triggers unbounded recursive execution that exhausts the server process's available resources, causing the affected node to terminate. The node does not recover automatically and requires manual intervention to restore service. |
| CVE-2026-103005 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user with connector management privileges could cause the cluster to allocate an uncontrolled amount of memory when connector resources with an excessively large `description` field are created and subsequently accessed, exhausting available heap memory and crashing the affected node. |
| CVE-2026-102411 | Medium | 2026-10-06 | Not applicable | No public exploit | Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to Denial of Service via Excessive Allocation (CAPEC-130). Elasticsearch enforces a size limit on the user-supplied metadata field for each individual template resource, but does not limit the total memory used when multiple such resources are retrieved together. A user holding the *manage_index_templates* cluster privilege can register multiple resources each within the individual limit. Retrieving them together materializes all of their metadata values in memory at once, exhausting available heap and causing the affected node to fail with an out-of-memory error, resulting in a denial of service. |
| CVE-2026-102409 | Medium | 2026-10-06 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can allow an authenticated user with low privileges to terminate an Elasticsearch node, resulting in denial of service, via Excessive Allocation (CAPEC-130). |
| CVE-2026-102408 | Medium | 2026-10-06 | Not applicable | No public exploit | Inefficient Regular Expression Complexity (CWE-1333) in Elasticsearch can lead to denial of service via Regular Expression Exponential Blowup (CAPEC-492). The ES|QL CHUNK function's recursive chunking strategy accepts a list of user-supplied regular expressions used as text-splitting separators, without validating their computational complexity or bounding their execution time. An authenticated user with read access to any text-based index can submit a specially crafted regular expression that triggers catastrophic backtracking, consuming excessive CPU on Elasticsearch worker threads and degrading query throughput for other tenants on the affected node. The cluster does not crash as a result of this issue. |
| CVE-2026-102407 | Medium | 2026-10-06 | Not applicable | No public exploit | Incorrect Authorization (CWE-863) in Elasticsearch can lead to unauthorized data stream modification via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user with sufficient privileges over a single resource could use the Modify Data Streams API to modify a data stream to which they were not otherwise authorized, potentially injecting data into it or affecting its ability to be searched normally. This issue does not allow an attacker to read the contents of a data stream they do not otherwise have access to. |
| CVE-2026-102404 | Medium | 2026-10-06 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can submit a specially crafted query that causes uncontrolled memory growth in the query processing engine, resulting in an out-of-memory condition that terminates the Elasticsearch node. The condition can be triggered repeatedly, including by queries embedded in shared resources, causing persistent cluster unavailability. |
| CVE-2026-94408 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130) |
| CVE-2026-94399 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130) |
| CVE-2026-94398 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130) |
| CVE-2026-94397 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130) |
| CVE-2026-94396 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130) |
| CVE-2026-82300 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). |
| CVE-2026-82294 | Medium | 2026-09-26 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). |
| CVE-2026-76717 | Medium | 2026-09-22 | Not applicable | No public exploit | A vulnerability exists in the Analytics and Location Engine (ALE) API that may allow for the disclosure of sensitive information. An unauthenticated remote attacker could exploit this vulnerability by providing specially crafted input to a specific API endpoint. Successful exploitation could result in the disclosure of sensitive user information, including password hashes, which could be used to facilitate further attacks. |
| CVE-2026-76716 | Medium | 2026-09-22 | Not applicable | No public exploit | Multiple vulnerabilities exist in the Analytics and Location Engine (ALE) that may allow for unauthorized access or denial of service. An unauthenticated remote attacker could exploit these vulnerabilities by sending specially crafted input or leveraging improper security configurations. Successful exploitation could result in a denial of service condition or unauthorized access to sensitive information. |
| CVE-2026-78605 | Medium | 2026-09-01 | Not applicable | No public exploit | Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') (CWE-444) in Elasticsearch can lead to information disclosure via HTTP Request Smuggling (CAPEC-33). Under specific proxy deployment configurations, a network attacker could obtain confidential responses intended for other authenticated users. |
| CVE-2026-56143 | Medium | 2026-09-01 | Not applicable | No public exploit | Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted request that causes excessive memory consumption, which may render the affected node unavailable. |
| CVE-2025-36290 | Medium | 2026-08-28 | Not applicable | No public exploit | IBM Integrated Analytics System 1.0.0.0 through 1.0.31.0 does not validate or improperly validates TLS certificate validation, which could allow an attacker to obtain sensitive information using man in the middle techniques. |
| CVE-2025-36271 | Medium | 2026-08-28 | Not applicable | No public exploit | IBM Integrated Analytics System 1.0.0.0 through 1.0.31.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. |
| CVE-2026-72687 | Medium | 2026-08-13 | Not applicable | No public exploit | A flaw in Elasticsearch allows a low-privileged authenticated user to submit a single small request containing a forged opaque identifier. Elasticsearch decodes and deserializes the identifier before confirming that it was legitimately issued by the cluster, and a size value carried inside the identifier drives an allocation that is neither capped nor accounted for by the available memory-usage controls. The resulting out-of-memory condition is fatal and terminates the affected node process, resulting in a denial of service. |
| CVE-2026-72686 | Medium | 2026-08-13 | Not applicable | No public exploit | A flaw in Elasticsearch allows a low-privileged authenticated user to submit a single request containing a crafted user-supplied input. A specific internal component validates the input using a recursive routine and applies no bound to the length of the value being validated, so the validation causes the thread to exhaust its stack. The resulting fatal error is not handled by the surrounding execution paths and terminates the affected node process, producing a denial of service. |
| CVE-2026-72685 | Medium | 2026-08-13 | Not applicable | No public exploit | A flaw in Elasticsearch allows a low-privileged authenticated user who can index documents to submit a single small document containing a crafted user-supplied input. Processing one such document occupies a worker thread from a bounded pool for a disproportionate amount of time, degrading the availability of indexing operations on the affected node. |
| CVE-2026-72684 | Medium | 2026-08-13 | Not applicable | No public exploit | A flaw in Elasticsearch allows an authenticated user holding only read privileges to submit a small search request containing a crafted user-supplied input. Processing that input causes a specific internal component to allocate memory without any upper bound, and the allocation occurs outside the scope of the existing memory accounting controls that were intended to constrain it. The resulting out-of-memory condition is fatal and terminates the affected node process, causing a denial of service. |
| CVE-2026-72683 | Medium | 2026-08-13 | Not applicable | No public exploit | A flaw in Elasticsearch allows an authenticated user with the privileges required to invoke the simulate pipeline API endpoint (https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ingest-simulate) to submit a request that causes a self-referential data structure to be created. When a specific internal component later processes that structure, the operation recurses without bound and raises a fatal error that is not handled by the surrounding execution path, terminating the affected node process and resulting in a denial of service. |
| CVE-2026-72679 | Medium | 2026-08-13 | Not applicable | No public exploit | Elasticsearch does not apply its configurable input length restriction to a user-supplied pattern accepted by an intervals query. Compiling a deeply nested pattern drives unbounded recursion that exhausts the thread stack and raises a fatal error, terminating the Elasticsearch node process and causing a denial of service for that node. An authenticated user holding only read-only privileges on a single searchable index can trigger the condition with one small search request. |
| CVE-2026-72678 | Medium | 2026-08-13 | Not applicable | No public exploit | Elasticsearch does not validate a size value taken from a user-supplied input before that value is used to reserve memory for an internal data structure. An authenticated user holding only read privileges can submit a single small crafted request to a product API endpoint that causes the node to attempt an excessively large allocation. The resulting memory exhaustion raises a fatal error that terminates the Elasticsearch node process, causing a denial of service for the affected node and degrading cluster health. The defect is not volumetric, so a single request is sufficient regardless of the heap size configured on the target node. |
| CVE-2026-72656 | Medium | 2026-08-13 | Not applicable | No public exploit | Memory Allocation with Excessive Size Value (CWE-789) in the ES|QL query processing of Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user able to submit ES|QL queries could send a specially crafted query whose evaluation allocates an unbounded amount of heap memory, exhausting the available heap on the receiving node and causing the node to become unavailable. |
| CVE-2026-72647 | Medium | 2026-08-13 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via Serialized Data with Nested Payloads (CAPEC-230). An authenticated user holding only read privileges on a single index can submit one specially crafted search request whose deeply nested structure is processed without a depth limit, exhausting the thread stack and terminating the affected node. |
| CVE-2026-72645 | Medium | 2026-08-13 | Not applicable | No public exploit | Memory Allocation with Excessive Size Value (CWE-789) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only read privileges on a single index can submit one small, specially crafted search request that causes an excessively large memory allocation, exhausting the JVM heap and terminating the affected node. |
| CVE-2026-72639 | Medium | 2026-08-13 | Not applicable | No public exploit | Elasticsearch does not enforce an upper bound on a user-supplied count accepted by a search highlighting option, and the allocation derived from that count is not accounted against any circuit breaker. An authenticated user holding only read privileges on a single searchable index can submit one small search request that causes the node to reserve an excessively large internal data structure. The allocation occurs before the existing highlighting safety limits are evaluated, so memory exhaustion raises a fatal error that terminates the Elasticsearch node process. This results in a denial of service for the affected node and degrades cluster routing and health. The defect is not volumetric and does not depend on the size of the indexed data, so a single request is sufficient. |
| CVE-2026-72638 | Medium | 2026-08-13 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via Input Data Manipulation (CAPEC-153). An authenticated user holding only low-privileged index creation permissions can submit a single request containing a specially crafted, malformed custom analysis definition that is resolved recursively without a cycle or depth check, exhausting the thread stack and terminating the affected node. |
| CVE-2026-72636 | Medium | 2026-08-13 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in the Elasticsearch wildcard matching helper can lead to a denial of service via Excessive Allocation (CAPEC-130). The matcher used to resolve wildcard patterns against names is implemented recursively and had no bound on recursion depth or on the total number of match operations performed. A search request containing a wildcard pattern with a large number of wildcard groups, evaluated against a sufficiently long name, exhausts the thread stack. Elasticsearch treats a stack overflow as an unrecoverable condition and shuts the node down, so the request terminates the affected node rather than failing gracefully. |
| CVE-2026-24078 | Medium | 2026-08-04 | Not applicable | No public exploit | Information Disclosure when IPSec negotiation fails or is not established properly during NG-eCall SIP signaling. |
| CVE-2026-24077 | Medium | 2026-08-04 | Not applicable | No public exploit | Information Disclosure when processing wireless network channel switch information with improperly formatted length fields. |
| CVE-2024-40683 | Medium | 2026-07-30 | Not applicable | No public exploit | IBM Operations Analytics - Log Analysis 1.3.5.0, 1.3.5.1, 1.3.5.2, 1.3.5.3, 1.3.6.0, 1.3.6.1, 1.3.7.0, 1.3.7.1, 1.3.7.2, and 1.3.8.0, 1.3.8.1, 1.3.8.2, 1.3.8.3, 1.3.8.4 does not invalidate session after a password chance which could allow an authenticated user to impersonate another user on the system. |
| CVE-2026-63263 | Medium | 2026-07-22 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Exponential Data Expansion (CAPEC-197). An authenticated user may submit a specially crafted query to the ES|QL engine that causes exponential CPU consumption during query evaluation. Because the resource exhaustion persists beyond query completion, repeated requests can fully exhaust the available query worker resources, rendering ES|QL queries unavailable until the node is restarted. |
| CVE-2026-63144 | Medium | 2026-07-21 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation. |
| CVE-2026-63140 | Medium | 2026-07-21 | Not applicable | No public exploit | Reachable Assertion (CWE-617) in Elasticsearch can lead to denial of service via Input Data Manipulation (CAPEC-153). A specially crafted search request containing a null value in a specific query clause causes an internal assertion to be raised during query parsing. Because Elasticsearch treats assertion failures as fatal errors, this terminates the affected node process. A low-privileged authenticated user with read access to at least one index can exploit this condition with a single request to cause a node to terminate, disrupting search availability. In a single-node deployment this fully stops Elasticsearch; in a multi-node cluster it reduces cluster capacity for each affected node. |
| CVE-2026-63136 | Medium | 2026-07-21 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A user with search privileges can submit a specially crafted search request that causes a data node to exhaust available heap memory, resulting in node unavailability and cluster degradation. An attacker could leverage this vulnerability to cause cluster downtime requiring manual intervention to restore service. |
| CVE-2026-61176 | Medium | 2026-07-21 | No exploit published | No public exploit | Vulnerability in the Oracle Product Lifecycle Analytics product of Oracle Supply Chain (component: Installation Issues). The supported version that is affected is 3.6.1. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Product Lifecycle Analytics. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Product Lifecycle Analytics accessible data as well as unauthorized access to critical data or complete access to all Oracle Product Lifecycle Analytics accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Product Lifecycle Analytics. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L). |
| CVE-2026-56145 | Medium | 2026-07-21 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user with permission to execute EQL sequence queries against an index they control can send a specially crafted query that triggers excessive memory consumption, causing the Elasticsearch node to crash. |
| CVE-2026-56144 | Medium | 2026-07-21 | Not applicable | No public exploit | Incorrect Authorization (CWE-863) in Elasticsearch can allow an authenticated user with limited index privileges to exploit insufficient authorization controls in the ingest simulation feature. By targeting indices they are not authorized to access directly, the user can cause those indices' configured ingest pipelines to execute and return their output, potentially disclosing data processed or enriched by those pipelines. Additionally, the same feature can be used to retrieve index mapping metadata for indices the user are not authorized to access directly. |
| CVE-2026-15995 | Medium | 2026-07-17 | Not applicable | No public exploit | IBM Cognos Analytics 12.1.3 GA Version with build number through 12.1.3-2606251736 could allow an attacker to obtain incorrect report summary results or cause report-processing failures due to a race condition in the Agentic AI assistant's concurrent request-handling logic when multiple authenticated users submit report-related tasks simultaneously. |
| CVE-2026-56456 | Medium | 2026-07-16 | Not applicable | No public exploit | HCL DFXAnalytics is affected by an Internal File Path Disclosure vulnerability. The application dashboard inadvertently leaks sensitive information regarding its internal file structure and directory paths through unhandled error messages, system logs, or debugging output, which could allow a remote attacker to map the underlying server environment and identify targets for further exploitation. |
| CVE-2026-35143 | Medium | 2026-07-16 | Not applicable | No public exploit | HCL DFXAnalytics is affected by a Missing SameSite Attribute vulnerability. The application fails to set the "SameSite" attribute on session cookies generated during authentication, which could allow a remote attacker to execute Cross-Site Request Forgery (CSRF) attacks if additional mitigations, such as Anti-CSRF tokens, are not implemented. |
| CVE-2026-35141 | Medium | 2026-07-16 | Not applicable | No public exploit | HCL DFXAnalytics is affected by a Login Replay Attack vulnerability. The application allows a remote attacker to intercept, delay, or fraudulently retransmit valid authentication data to achieve unauthorized access. To mitigate this risk, the application must implement a mechanism to include timestamps with every message, ensuring that messages exceeding a specific age threshold are automatically rejected by the recipient system. |
| CVE-2026-15082 | Medium | 2026-07-10 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Siteimprove Analytics allows Cross-Site Scripting (XSS). This issue affects Siteimprove Analytics versions: from 0.0.0 to 2.0.1. |
| CVE-2026-46453 | Medium | 2026-07-06 | No exploit published | No public exploit | Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel ElasticSearch Rest Client. The camel-elasticsearch-rest-client component reads several Exchange headers to control its behaviour - SEARCH_QUERY (an advanced query body), OPERATION (which Elasticsearch operation to run), INDEX_NAME, INDEX_SETTINGS and ID. The string values of these header constants, defined in ElasticSearchRestClientConstant, are plain unprefixed names ('SEARCH_QUERY', 'OPERATION', 'INDEX_NAME', 'INDEX_SETTINGS', 'ID') rather than the 'Camel'-prefixed names used by every other Camel component (for example CamelSqlQuery, CamelMongoDbCriteria, CamelCqlQuery). Camel's inbound HTTP header filter, HttpHeaderFilterStrategy, blocks only header names that begin with 'Camel' or 'camel'. Because the Elasticsearch header names do not carry that prefix, they pass through the inbound filter unchanged. When a Camel route exposes an HTTP entry point (for example platform-http) in front of an elasticsearch-rest-client producer, an untrusted HTTP client can set these headers directly on its request and override the query and operation that the route author configured: reading every document in the index (SEARCH_QUERY with a match_all query), deleting documents (OPERATION set to Delete together with ID), or exfiltrating selected fields. No credentials are required and the producer reads the headers unconditionally. This issue affects Apache Camel: from 4.3.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix renames the camel-elasticsearch-rest-client Exchange header constant string values (ID, SEARCH_QUERY, INDEX_SETTINGS, INDEX_NAME, OPERATION) to carry the Camel prefix (CamelElasticsearchId, CamelElasticsearchSearchQuery, CamelElasticsearchIndexSettings, CamelElasticsearchIndexName, CamelElasticsearchOperation) so that they are blocked by the inbound HttpHeaderFilterStrategy; the Java field names are unchanged. For deployments that cannot upgrade immediately, strip the affected headers from untrusted inbound messages before they reach the producer (for example removeHeader('SEARCH_QUERY'), removeHeader('OPERATION'), removeHeader('INDEX_NAME'), removeHeader('INDEX_SETTINGS') and removeHeader('ID') in front of the elasticsearch-rest-client endpoint), or apply a custom HeaderFilterStrategy that blocks these names. |
| CVE-2026-56149 | Medium | 2026-07-01 | Not applicable | No public exploit | Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted machine learning request that causes excessive memory consumption, which may render the affected node unavailable. |
| CVE-2026-56148 | Medium | 2026-07-01 | Not applicable | No public exploit | Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user can submit a specially crafted query that causes excessive resource consumption while the request is processed, which may render the affected node unavailable. |
| CVE-2026-49090 | Medium | 2026-07-01 | Not applicable | No public exploit | Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user can submit a specially crafted bulk request that causes sustained high CPU consumption, which can render the affected node unable to process requests. |
| CVE-2025-59610 | Medium | 2026-06-01 | Not applicable | No public exploit | Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer. |
| CVE-2025-59609 | Medium | 2026-06-01 | Not applicable | No public exploit | Information Disclosure when processing advertisement frames with malformed MBSSID elements of insufficient length. |
| CVE-2026-2255 | Medium | 2026-05-27 | No exploit published | No public exploit | Hitachi Vantara Pentaho Data Integration & Analytics versions before 10.2.0.6 and 11.0.0.0, including 9.3.x and 8.3.x, expose Hadoop cluster credentials in plain text through the Cluster Test API. Although the user should not see those explicitly, the defect is mitigated by the fact the user can already leverage those credentials to submit jobs under the same account through the backend API. |
| CVE-2026-2254 | Medium | 2026-05-27 | No exploit published | No public exploit | Hitachi Vantara Pentaho Data Integration & Analytics versions before 10.2.0.6 and 11.0.0.0, including 9.3.x and 8.3.x, does not apply ACLs on certain API endpoints related to platform mail notfications. |
| CVE-2026-42408 | Medium | 2026-05-13 | Not applicable | No public exploit | When BIG-IP DNS is provisioned, a vulnerability exists in an undisclosed TMOS Shell (tmsh) command that may allow a highly privileged authenticated attacker to view sensitive information. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-42063 | Medium | 2026-05-13 | Not applicable | No public exploit | A vulnerability exists in iControl SOAP where an authenticated attacker with the Resource Administrator or Administrator role can download sensitive files. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-42058 | Medium | 2026-05-13 | Not applicable | No public exploit | An authenticated attacker's undisclosed requests to BIG-IP iControl REST can lead to an information leak of BIG-IP local user account names. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-41954 | Medium | 2026-05-13 | Not applicable | No public exploit | Sensitive information disclosure vulnerability exists in the undisclosed iControl REST endpoint and TMOS Shell (tmsh) command which may allow an authenticated attacker with resource administrator role privileges to view sensitive information. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-40703 | Medium | 2026-05-13 | Not applicable | No public exploit | A cross-site request forgery (CSRF) vulnerability exists in the dashboard of the BIG-IP Configuration utility. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-40435 | Medium | 2026-05-13 | Not applicable | No public exploit | When configured, IP-based access restrictions for httpd do not cover all endpoints, which may allow connections from blocked addresses. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-34019 | Medium | 2026-05-13 | Not applicable | No public exploit | When Bidirectional Forwarding Detection (BFD) is configured in Static and Dynamic routing protocols, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to stop processing BFD packets and cause the configured routing protocol to fail over. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-24464 | Medium | 2026-05-13 | Not applicable | No public exploit | When running in Appliance mode, a directory traversal vulnerability exists in an undisclosed iControl REST endpoint that may allow an authenticated attacker with administrator role privileges to cross a security boundary and delete files. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated. |
| CVE-2026-41018 | Medium | 2026-05-11 | Not applicable | No public exploit | The Elasticsearch logging provider, when configured with a `host` URL that embeds credentials (for example `https://user:password@server.example.com:9200`), wrote the full host URL — including the embedded credentials — into task logs. Any user with task-log read permission could harvest the backend credentials. Users are advised to upgrade to `apache-airflow-providers-elasticsearch` 6.5.3 or later and, as a defense-in-depth measure, configure the backend credentials via a secret backend rather than embedding them in the `[elasticsearch] host` URL. |
| CVE-2025-59854 | Medium | 2026-05-06 | Not applicable | No public exploit | HCL DFXAnalytics is affected by an Insecure Security Header Configuration vulnerability where the application utilizes the outdated X-XSS-Protection header, which could allow an attacker to exploit browser-specific rendering flaws or bypass security controls that should instead be managed by a robust Content Security Policy (CSP). |
| CVE-2025-59853 | Medium | 2026-05-06 | Not applicable | No public exploit | HCL DFXAnalytics is affected by an Improper Error Handling vulnerability where the application exposes detailed stack traces in responses, which could allow an attacker to gain insights into the application's internal structure, code logic, and environment configurations. |
| CVE-2025-31970 | Medium | 2026-05-06 | Not applicable | No public exploit | HCL DFXAnalytics is affected by an Insecure Security Header configuration vulnerability where the Content-Security-Policy does not define strict directives for object-src and base-uri, which could allow an attacker to exploit injection vectors such as Cross-Site Scripting (XSS) |
| CVE-2026-40970 | Medium | 2026-04-27 | No exploit published | No public exploit | When configured to use an SSL bundle, Spring Boot's Elasticsearch auto-configuration does not perform hostname verification when connecting to the Elasticsearch server. Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory. |
| CVE-2026-0827 | Medium | 2026-04-15 | Not applicable | Proof of concept only | During an internal security assessment, a potential vulnerability was discovered in Lenovo Diagnostics and the HardwareScanAddin used in Lenovo Vantage that, during installation or when using hardware scan, could allow a local authenticated user to perform an arbitrary file write with elevated privileges. |
| CVE-2026-5584 | Medium | 2026-04-05 | Not applicable | Proof of concept only | A vulnerability has been found in Fosowl agenticSeek 0.1.0. Impacted is the function PyInterpreter.execute of the file sources/tools/PyInterpreter.py of the component query Endpoint. Such manipulation leads to code injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way. |
| CVE-2026-3529 | Medium | 2026-03-26 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Google Analytics GA4 allows Cross-Site Scripting (XSS).This issue affects Google Analytics GA4: from 0.0.0 before 1.1.14. |
| CVE-2026-1267 | Medium | 2026-03-17 | Not applicable | No public exploit | IBM Planning Analytics Local 2.1.0 through 2.1.17 could allow an unauthorized access to sensitive application data and administrative functionalities due to lack of proper access controls. |
| CVE-2025-14806 | Medium | 2026-03-17 | Not applicable | No public exploit | IBM Planning Analytics Local 2.1.0 through 2.1.17 could allow an attacker to trick the caching mechanism into storing and serving sensitive, user-specific responses as publicly cacheable resources. |
| CVE-2025-36105 | Medium | 2026-03-10 | Not applicable | No public exploit | IBM Planning Analytics Advanced Certified Containers 3.1.0 through 3.1.4 could allow a local privileged user to obtain sensitive information from environment variables. |
| CVE-2025-47371 | Medium | 2026-03-02 | Not applicable | No public exploit | Transient DOS when an LTE RLC packet with invalid TB is received by UE. |
| CVE-2026-0947 | Medium | 2026-02-04 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal AT Internet Piano Analytics allows Cross-Site Scripting (XSS).This issue affects AT Internet Piano Analytics: from 0.0.0 before 1.0.1, from 2.0.0 before 2.3.1. |
| CVE-2025-47369 | Medium | 2026-01-07 | Not applicable | No public exploit | Information disclosure when a weak hashed value is returned to userland code in response to a IOCTL call to obtain a session ID. |
| CVE-2025-47344 | Medium | 2026-01-07 | Not applicable | No public exploit | Memory corruption while handling sensor utility operations. |
| CVE-2025-47334 | Medium | 2026-01-07 | Not applicable | No public exploit | Memory corruption while processing shared command buffer packet between camera userspace and kernel. |
| CVE-2025-47333 | Medium | 2026-01-07 | Not applicable | No public exploit | Memory corruption while handling buffer mapping operations in the cryptographic driver. |
| CVE-2025-47331 | Medium | 2026-01-07 | Not applicable | No public exploit | Information disclosure while processing a firmware event. |
| CVE-2025-47330 | Medium | 2026-01-07 | Not applicable | No public exploit | Transient DOS while parsing video packets received from the video firmware. |