Overview 5,089 matches · 260 in Waratek scope · 15 protected · 6 exploited · 2 CISA KEV · 111 public PoC · 7 EPSS ≥ 0.5
5,089matches
260in Waratek scope5.1%
15protected0.3%
6exploited0.1%
2CISA KEV0.0%
111public PoC2.2%
7EPSS ≥ 0.50.1%
Protected by Waratek
15
0.3%
Rule in development
0
0.0%
Mitigation candidate
7
0.1%
No exploit published
238
4.7%
Outside Waratek scope
61
1.2%
Not applicable
4,768
93.7%
Withdrawn CVE
0
0.0%
blocked by ARMR today
15
0.3%
partly blocked
0
0.0%
not blocked
5,074
99.7%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 458 / year
19964
Not applicable4
Medium4
not blocked4
Working exploit published2
No public exploit2
19978
Not applicable8
Medium8
not blocked8
No public exploit8
19987
Not applicable7
Medium7
not blocked7
Working exploit published1
No public exploit6
19994
Not applicable4
Medium4
not blocked4
Working exploit published2
No public exploit2
20005
Mitigation candidate1
Not applicable4
Medium5
not blocked5
Working exploit published2
No public exploit3
200126
Mitigation candidate1
No exploit published2
Outside Waratek scope1
Not applicable22
Medium26
not blocked26
Working exploit published6
No public exploit20
200216
No exploit published1
Not applicable15
Medium16
not blocked16
Working exploit published3
No public exploit13
200312
Not applicable12
Medium12
not blocked12
Working exploit published2
No public exploit10
200418
Outside Waratek scope1
Not applicable17
Medium18
not blocked18
Working exploit published7
No public exploit11
200532
Mitigation candidate1
No exploit published6
Not applicable25
Medium32
not blocked32
Working exploit published5
No public exploit27
200646
Mitigation candidate1
No exploit published9
Not applicable36
Medium46
not blocked46
Working exploit published6
No public exploit40
200756
Mitigation candidate1
No exploit published9
Not applicable46
Medium56
not blocked56
Working exploit published5
No public exploit51
200867
No exploit published5
Not applicable62
Medium67
not blocked67
Working exploit published4
No public exploit63
200983
Mitigation candidate1
No exploit published20
Outside Waratek scope1
Not applicable61
Medium83
not blocked83
Working exploit published11
No public exploit72
2010130
No exploit published20
Not applicable110
Medium130
not blocked130
Working exploit published15
No public exploit115
201199
Protected by Waratek1
Mitigation candidate1
No exploit published22
Outside Waratek scope1
Not applicable74
Medium99
blocked by ARMR today1
not blocked98
Working exploit published4
No public exploit95
2012111
Protected by Waratek1
No exploit published17
Not applicable93
Medium111
blocked by ARMR today1
not blocked110
Working exploit published7
No public exploit104
2013236
Protected by Waratek1
No exploit published16
Outside Waratek scope1
Not applicable218
Medium236
blocked by ARMR today1
not blocked235
Working exploit published2
No public exploit234
2014282
Protected by Waratek2
No exploit published22
Outside Waratek scope2
Not applicable256
Medium282
blocked by ARMR today2
not blocked280
Exploited3
Working exploit published11
No public exploit268
2015148
No exploit published11
Not applicable137
Medium148
not blocked148
Working exploit published1
No public exploit147
2016225
No exploit published6
Outside Waratek scope2
Not applicable217
Medium225
not blocked225
Working exploit published2
No public exploit223
2017458
No exploit published5
Outside Waratek scope3
Not applicable450
Medium458
not blocked458
Working exploit published3
No public exploit455
2018417
Protected by Waratek2
No exploit published9
Outside Waratek scope8
Not applicable398
Medium417
blocked by ARMR today2
not blocked415
Working exploit published4
No public exploit413
2019303
Protected by Waratek2
No exploit published10
Outside Waratek scope5
Not applicable286
Medium303
blocked by ARMR today2
not blocked301
Exploited2
No public exploit301
2020337
Protected by Waratek2
No exploit published7
Outside Waratek scope4
Not applicable324
Medium337
blocked by ARMR today2
not blocked335
Exploited1
No public exploit336
2021396
Protected by Waratek1
No exploit published2
Outside Waratek scope13
Not applicable380
Medium396
blocked by ARMR today1
not blocked395
No public exploit396
2022268
No exploit published12
Outside Waratek scope14
Not applicable242
Medium268
not blocked268
No public exploit268
2023191
No exploit published4
Not applicable187
Medium191
not blocked191
No public exploit191
2024303
Protected by Waratek2
No exploit published10
Outside Waratek scope5
Not applicable286
Medium303
blocked by ARMR today2
not blocked301
Working exploit published3
Proof of concept only1
No public exploit299
2025360
No exploit published4
Not applicable356
Medium360
not blocked360
Proof of concept only1
No public exploit359
2026441
Protected by Waratek1
No exploit published9
Not applicable431
Medium441
blocked by ARMR today1
not blocked440
No public exploit441
19961999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-84229 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2.4 could allow a remote attacker to bypass security restrictions due to improper validation of CSRF tokens for GET requests. |
| CVE-2026-84030 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2.4 could allow a remote attacker to execute arbitrary SQL commands due to improper neutralization of special elements used in an SQL command. |
| CVE-2026-82830 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2.4 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of argument delimiters. |
| CVE-2026-81542 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to delete arbitrary files due to path traversal. |
| CVE-2026-80435 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw. |
| CVE-2026-18484 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM ContextForge MCP Gateway 1.0.0 through 1.0.11 could allow a remote authenticated attacker to cause a denial of service due to improper slug normalization causing tool name collisions. |
| CVE-2026-18196 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2, and 12.0.1.0 through 12.0.12.30 could allow a remote attacker to inject arbitrary HTML due to improper output neutralization. |
| CVE-2026-18195 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2, and 12.0.1.0 through 12.0.12.30 could allow a remote attacker to perform content spoofing due to improper output encoding of error messages. |
| CVE-2026-17437 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2, and 12.0.1.0 through 12.0.12.29 could allow a local attacker to perform an arbitrary file write due to improper validation of pathnames during archive extraction. |
| CVE-2026-16433 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to write arbitrary files due to a path traversal vulnerability. |
| CVE-2026-16427 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to write arbitrary files due to a path traversal vulnerability. |
| CVE-2026-16325 | Medium | 2026-11-08 | Not applicable | No public exploit | IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary scripts due to improper neutralization of input in the X-Forwarded-Host header. |
| CVE-2026-17305 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery. |
| CVE-2026-17304 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper input validation. Locations supplied when service definitions are imported are not sufficiently validated, which could allow the server to retrieve content it should not access. |
| CVE-2026-17303 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to access internal network resources due to improper validation of a user-supplied URL. The address is not sufficiently restricted, which could allow the server to contact internal systems. |
| CVE-2026-17302 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to probe internal network services due to improper validation of a user-supplied URL. |
| CVE-2026-17241 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper authorization. |
| CVE-2026-17240 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to bypass security restrictions due to improper authentication. Authentication checks are not applied consistently, which could allow protected resources to be reached without valid credentials. |
| CVE-2026-17238 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information from other tenants due to path parameter injection. Values in the request path are not sufficiently validated, which could allow access to data belonging to other tenants. |
| CVE-2026-17237 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery. |
| CVE-2026-17236 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper authorization. Authorization checks are not applied when certain organization URLs are resolved, which could allow access to information belonging to others. |
| CVE-2026-17233 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain information about internal network services due to improper validation of user-supplied URLs. Addresses supplied by users are not sufficiently restricted, so the server could be made to contact internal systems. |
| CVE-2026-17232 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to bypass security restrictions due to improper neutralization of special elements in a request. Specially formed request parameters are not handled safely, which could allow protections to be circumvented. |
| CVE-2026-17231 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to an observable response discrepancy. |
| CVE-2026-17230 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to a path traversal vulnerability. |
| CVE-2026-17225 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass security restrictions and access unauthorized analytics queries due to improper input validation. Request parameters are not validated sufficiently, which could allow restrictions on analytics data to be circumvented. |
| CVE-2026-17215 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to verbose error messages. Error responses contain more information about the system than necessary, which could help an attacker learn about the environment. |
| CVE-2026-17202 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to enumerate usernames due to observable differences in response behavior. |
| CVE-2026-17139 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary scripts due to cross-site scripting. Certain URL fields are not sufficiently validated, so malicious script content could run in another user's browser session. |
| CVE-2026-17137 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a local attacker to obtain sensitive information due to improper use of cryptography. The encryption applied to stored data is not implemented with sufficient strength, which weakens its protection. |
| CVE-2026-17128 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to the insertion of sensitive information into log files. |
| CVE-2026-17098 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to verbose error messages. |
| CVE-2026-17085 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass security restrictions due to improper handling of case sensitivity. An access restriction is not applied consistently to all variations of the input, which could allow it to be circumvented and unauthorized emails to be sent. |
| CVE-2026-17067 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to access internal network resources due to server-side request forgery. |
| CVE-2026-17064 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to an insecure direct object reference. |
| CVE-2026-16719 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to view arbitrary files on the system due to a path traversal vulnerability. A specially crafted URL request could allow directories outside the intended location to be accessed. |
| CVE-2026-16711 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to inject platform credentials into outbound requests due to improper input validation. A validation check is not sufficiently strict, which could cause platform credentials to be included in outbound requests. |
| CVE-2026-16710 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to a server-side request forgery vulnerability. |
| CVE-2026-16679 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to view arbitrary files on the system due to a path traversal vulnerability. A specially crafted URL request could allow directories outside the intended location to be accessed. |
| CVE-2026-108178 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a token to be accepted that should be rejected due to an improperly implemented security check. Under certain conditions, token validation is incomplete, so a token may be accepted for a purpose it was not intended for. |
| CVE-2026-105459 | Medium | 2026-11-07 | Not applicable | No public exploit | IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow an attacker to gain unauthorized access to an organization due to improper verification of a cryptographic signature. A token is accepted without its signature being fully verified, which could allow an attacker to join an organization without a valid invitation. |
| CVE-2026-19319 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Watson Speech Services Cartridge 4.0.0 through 5.4.0 could allow a remote attacker to obtain sensitive information due to an out-of-bounds read. |
| CVE-2026-16725 | Medium | 2026-11-04 | Not applicable | No public exploit | IBM Watson Speech Services Cartridge 4.0.0 through 5.4.0 could allow a remote authenticated attacker to read arbitrary files from the local filesystem due to path traversal. |
| 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-93744 | Medium | 2026-10-20 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow an unathenticated remote attacker to bypass security restrictions due to improper access control. By sending a specially crafted HTTP request to any URL within the Navigator application prior to authentication, a bad actor could exploit this vulnerability to alter server-side session security state. |
| CVE-2026-8355 | Medium | 2026-10-20 | Not applicable | No public exploit | IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 is vulnerable to a server-side request Forgery (SSRF) that allows authenticated users with gateway creation privileges to perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints. The vulnerability occurs during OAuth-enabled gateway registration when the system fails to validate the oauth_config.token_url parameter. When registering a gateway with OAuth client credentials authentication, an attacker can supply a malicious token_url pointing to internal services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure), or localhost-bound services. The application immediately performs an HTTP POST request to the attacker-controlled URL with form-encoded credentials in the body. If the response cannot be parsed as a valid OAuth token response, up to 256 characters of the response body are reflected back to the attacker in the HTTP 502 error message. This vulnerability bypasses existing SSRF protections that are applied to the gateway.url field but not to OAuth configuration parameters. |
| CVE-2026-4418 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Cloud Pak System 2.3.6.0, and 2.3.6.1 is vulnerable to HTML injection. A remotely authenticated attacker could inject malicious HTML code, which when viewed, would be executed in the victim's Web browser within the security context of the hosting site. |
| CVE-2026-4413 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Concert 1.0 through 3.0.0 is vulnerable to cross-site scripting. This vulnerability allows an unauthenticated attacker 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-4405 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Concert 1.0 through 3.0.0 allows web page cache to be stored locally which can be read by another user on the system. |
| CVE-2026-3628 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Concert 1.0 through 3.0.0 allows information disclosure through exposure of schema suggestions. |
| CVE-2026-15661 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Concert 1.0 through 3.0.0 could allow an unauthorized user to inject data into log messages due to improper neutralization of special elements when written to log files. |
| CVE-2026-1510 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Concert 1.0 through 3.0.0 is vulnerable to Information Disclosure via Heap Inspection. |
| CVE-2026-14511 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ 9.4.5.0 through 9.4.5.1 could allow an authenticated user to cause a denial of service by sending a specially crafted message that crashes consuming applications. |
| CVE-2026-12727 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause potential process instability due to an off-by-one buffer overflow when processing specially crafted object names. |
| CVE-2026-12670 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause a denial of service through a specially crafted message that triggers excessive memory operations during character set conversion. |
| CVE-2026-12669 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to trigger a minor out-of-bounds read when sending malformed compressed data, though the data is not disclosed and the request is rejected. |
| CVE-2026-12350 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause a denial of service by sending a specially crafted asynchronous consume request that crashes the queue manager agent process. |
| CVE-2026-12343 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause a denial of service due to improper validation of RFH2 message header fields in queued publish/subscribe operations. |
| CVE-2026-12155 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause a denial of service by sending specially crafted multicast status messages that trigger a NULL pointer dereference. |
| CVE-2026-11831 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause a limited denial of service and obtain very limited information about process memory layout due to an out-of-bounds read when processing a specially crafted client request. |
| CVE-2026-11829 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow an authenticated attacker to cause a denial of service due to improper validation of offset values in MQOPEN requests. |
| CVE-2026-11828 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM MQ could allow a remote attacker with queue manager control or man-in-the-middle access on unencrypted channels to cause a denial of service in client applications using asynchronous message consumption due to improper validation of queue name length values. |
| CVE-2023-38375 | Medium | 2026-10-19 | Not applicable | No public exploit | IBM Cloud Pak System 2.3.6.0, and 2.3.6.1 is vulnerable to cross-site scripting. This vulnerability allows users 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-17491 | Medium | 2026-10-16 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 is could allow a remote authenticated attacker to bypass security restrictions due to improper enforcement of the ChrootDirectory configuration directive. |
| CVE-2026-17488 | Medium | 2026-10-16 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote authenticated attacker to bypass security restrictions due to improper authentication. |
| CVE-2026-17275 | Medium | 2026-10-16 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote attacker to perform unauthorized manipulation of distributed transactions due to improper validation of attacker-supplied transaction identifiers. |
| CVE-2026-17073 | Medium | 2026-10-16 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a local attacker to obtain sensitive information due to missing subtree checks during file handle resolution. |
| CVE-2026-17068 | Medium | 2026-10-16 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a local attacker to bypass NFS version restrictions due to improper enforcement of the export version flag. |
| CVE-2026-107674 | Medium | 2026-10-16 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 is vulnerable to a denial of service to Digital Certificate Manager (DCM) for System TLS using applications attempting to create secure network connections. A bad actor could use this to prevent a service from starting or cause it to fallback to non-secure connections. |
| CVE-2026-18343 | Medium | 2026-10-13 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a local attacker to modify the BOOTP table due to improper authorization. |
| CVE-2026-18318 | Medium | 2026-10-13 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote attacker to perform brute-force attacks to obtain credentials due to improper authentication. |
| CVE-2026-17487 | Medium | 2026-10-13 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote attacker to enumerate user profiles due to the return of distinct error codes during the sign-on process. |
| CVE-2026-17484 | Medium | 2026-10-13 | Not applicable | No public exploit | IBM i 7.3, 7.4, 7.5, and 7.6 could allow a local attacker to cause a denial of service due to improper access control. |
| 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-87980 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a local attacker to obtain sensitive information due to cleartext storage of sensitive information in logs. |
| CVE-2026-84290 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Guardium Data Protection 12.0, 12.1, 12.2 is affected by an improper validation of user-supplied pointers in the WfpMonitor kernel driver. Certain METHOD_NEITHER IOCTL handlers dereference user-controlled pointers without adequate probing and exception handling, potentially allowing a privileged local attacker to cause a system crash or perform limited kernel-memory reads. |
| CVE-2026-84274 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2.2 is affected by a sensitive information exposure vulnerability. During SECRET and API_KEY rotation processing, sensitive credential material is logged at INFO level by the edge-controller/edge-manager components. An authenticated attacker with access to the relevant application or container logs could obtain these credentials and use them to impersonate services or gain unauthorized access to the Guardium control plane. |
| CVE-2026-78407 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 are vulnerable to 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-78399 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow an authenticated user to cause a denial of service using a specially crafted HTTP query due to improper allocation of system resources |
| CVE-2026-19878 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a remote authenticated attacker to bypass additional authentication workflow steps. |
| CVE-2026-16830 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a remote authenticated attacker to modify data and cause a denial of service due to an SQL injection vulnerability. |
| CVE-2026-16182 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM DataPower Gateway 10.5.0.0 through 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 an attacker to cause a denial of service due to a NULL pointer dereference in GraphQL variable processing. |
| CVE-2026-16177 | Medium | 2026-10-08 | Not applicable | No public exploit | 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 authenticated attacker to obtain sensitive information due to an out-of-bounds read. |
| CVE-2026-14521 | Medium | 2026-10-08 | Not applicable | No public exploit | 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 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks. |
| CVE-2026-14509 | Medium | 2026-10-08 | Not applicable | No public exploit | 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 algorithmic complexity in linked-list traversal. |
| CVE-2026-14273 | Medium | 2026-10-08 | Not applicable | No public exploit | 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 local attacker to obtain sensitive information due to improper authorization. |
| CVE-2026-13258 | Medium | 2026-10-08 | Not applicable | No public exploit | 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 is vulnerable to 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-13257 | Medium | 2026-10-08 | Not applicable | No public exploit | 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 an authenticated user to forge signature requests due to improper verification of data authenticity. |
| CVE-2026-12091 | Medium | 2026-10-08 | Not applicable | No public exploit | IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a denial of service due to a heap-based out-of-bounds read. A remote attacker could send a specially crafted request that causes a limited out‑of‑bounds memory read. |