Overview 2,433 matches · 0 in Waratek scope · 0 protected · 48 exploited · 28 CISA KEV · 81 public PoC · 37 EPSS ≥ 0.5
2,433matches
0in Waratek scope0.0%
0protected0.0%
48exploited2.0%
28CISA KEV1.2%
81public PoC3.3%
37EPSS ≥ 0.51.5%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
2,433
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
2,433
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 363 / year
20001
Not applicable1
Medium1
not blocked1
No public exploit1
20010
20020
20032
Not applicable2
High2
not blocked2
Working exploit published2
20042
Not applicable2
Medium2
not blocked2
No public exploit2
20052
Not applicable2
Medium2
not blocked2
No public exploit2
20066
Not applicable6
High2
Medium4
not blocked6
No public exploit6
200716
Not applicable16
High2
Medium14
not blocked16
Working exploit published2
No public exploit14
20086
Not applicable6
High2
Medium3
Low1
not blocked6
Working exploit published1
No public exploit5
200913
Not applicable13
High12
Medium1
not blocked13
Exploited2
Working exploit published4
No public exploit7
20105
Not applicable5
High4
Medium1
not blocked5
Working exploit published1
No public exploit4
20115
Not applicable5
High3
Medium2
not blocked5
Working exploit published1
No public exploit4
201220
Not applicable20
High14
Medium5
Low1
not blocked20
Working exploit published2
No public exploit18
201327
Not applicable27
High11
Medium14
Low2
not blocked27
Exploited1
Working exploit published1
No public exploit25
201427
Not applicable27
High8
Medium14
Low5
not blocked27
Exploited1
Working exploit published1
No public exploit25
201527
Not applicable27
High4
Medium19
Low4
not blocked27
Working exploit published1
No public exploit26
201625
Not applicable25
Critical4
High13
Medium8
not blocked25
Working exploit published1
No public exploit24
201794
Not applicable94
Critical8
High21
Medium58
Low7
not blocked94
Working exploit published3
Proof of concept only1
No public exploit90
2018106
Not applicable106
Critical13
High44
Medium46
Low3
not blocked106
Exploited1
Working exploit published4
Proof of concept only1
Forecast only1
No public exploit99
2019146
Not applicable146
Critical12
High58
Medium71
Low5
not blocked146
Exploited4
Working exploit published6
Proof of concept only1
No public exploit135
2020178
Not applicable178
Critical42
High64
Medium68
Low4
not blocked178
Exploited2
Working exploit published1
Proof of concept only2
Forecast only1
No public exploit172
2021185
Not applicable185
Critical21
High103
Medium61
not blocked185
Exploited6
Working exploit published5
Proof of concept only1
Forecast only2
No public exploit171
2022186
Not applicable186
Critical19
High103
Medium61
Low3
not blocked186
Exploited2
Working exploit published4
Proof of concept only18
Forecast only2
No public exploit160
2023351
Not applicable351
Critical41
High211
Medium95
Low4
not blocked351
Exploited5
Working exploit published1
Proof of concept only22
Forecast only2
No public exploit321
2024363
Not applicable363
Critical29
High229
Medium103
Low2
not blocked363
Exploited3
Working exploit published2
Proof of concept only19
Forecast only1
No public exploit338
2025346
Not applicable346
Critical19
High193
Medium106
Low28
not blocked346
Exploited12
Working exploit published1
Proof of concept only46
Forecast only1
No public exploit286
2026294
Not applicable294
Critical15
High144
Medium126
Low9
not blocked294
Exploited9
Proof of concept only26
No public exploit259
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-88252 | Medium | 2026-10-06 | Not applicable | Proof of concept only | A flaw was found in sssd. A local user can cause a Denial of Service (DoS) by exhausting the responder service's available file descriptors (system handles used for open connections). By opening and maintaining many concurrent connections to a responder socket while continuing to queue new connection attempts, an attacker can trigger an unthrottled retry loop. This condition leads to high CPU utilization and stalls the service, preventing legitimate identity and authentication requests from being processed. |
| CVE-2026-57559 | High | 2026-10-06 | Not applicable | No public exploit | Memory corruption while processing service requests. |
| CVE-2026-57555 | High | 2026-10-06 | Not applicable | No public exploit | Memory Corruption when executing system service routines due to improper handling of user input buffers. |
| CVE-2026-57554 | High | 2026-10-06 | Not applicable | No public exploit | Memory Corruption when asynchronous threads access shared performance counter data simultaneously during FastRPC invocations. |
| CVE-2026-57545 | High | 2026-10-06 | Not applicable | No public exploit | Memory corruption when processing draw objects of incorrect type during graphics command list execution. |
| CVE-2026-57537 | High | 2026-10-06 | Not applicable | No public exploit | Memory Corruption when accessing and modifying geographic mapping data concurrently without proper synchronization. |
| CVE-2026-25302 | High | 2026-10-06 | Not applicable | No public exploit | Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed. |
| CVE-2026-25291 | High | 2026-10-06 | Not applicable | No public exploit | Memory corruption when performing concurrent operations on shared memory page lists due to lack of proper synchronization mechanisms. |
| CVE-2026-25274 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory Corruption when processing concurrent DMA buffer allocation and deallocation commands without proper synchronization. |
| CVE-2026-25273 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory Corruption when processing camera operations due to out-of-bounds write during driver updates. |
| CVE-2026-25272 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory Corruption when processing camera CRE driver operations with improper handling of buffer limits during hardware update preparation. |
| 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-25269 | Medium | 2026-10-06 | Not applicable | No public exploit | Memory corruption when processing camera requests with excessive batch and IO buffer configurations exceeds allocated memory size. |
| CVE-2026-25267 | High | 2026-10-06 | Not applicable | No public exploit | Memory corruption when non-secure loader rewrites page tables before secure memory initialization. |
| 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-104048 | High | 2026-10-06 | Not applicable | Proof of concept only | A flaw was found in SSSD. In trust-enabled identity management environments, SSSD evaluates Host-Based Access Control (HBAC) rules by stripping domain qualifiers and comparing only short usernames. An authenticated user in a trusted domain who shares the same username as an authorized local account can bypass access policies and gain unauthorized access to protected services or hosts. |
| CVE-2026-104047 | Medium | 2026-10-06 | Not applicable | No public exploit | A flaw was found in SSSD. When configured to use Microsoft Entra ID, search inputs are not properly sanitized before being incorporated into directory query filters. A local user can exploit this vulnerability by submitting a crafted lookup request, manipulating the query logic to cause unauthorized information disclosure from the directory. |
| CVE-2026-104046 | Medium | 2026-10-06 | Not applicable | No public exploit | A flaw was found in SSSD (System Security Services Daemon). When Identity Provider (IdP) authentication is enabled, pre-authentication requests retain state in memory without being cleared or timed out. A local attacker can repeatedly initiate authentication flows without completing them, causing unbounded memory consumption. This memory exhaustion can lead to a Denial of Service (DoS) by degrading or terminating SSSD authentication services. |
| CVE-2026-104045 | Medium | 2026-10-06 | Not applicable | Proof of concept only | A flaw was found in SSSD. A local user can trigger a Denial of Service (DoS) by exploiting a race condition in the autofs responder between asynchronous enumeration completion and map invalidation. By repeatedly sending concurrent map enumeration and invalidation requests, an attacker can cause memory to leak, leading to excessive memory consumption that can disrupt or crash the autofs service. |
| CVE-2026-104039 | Medium | 2026-10-06 | Not applicable | No public exploit | A flaw was found in SSSD. A local user can cause a denial of service (DoS) by disrupting system authentication services. When handling Generic Security Services Application Programming Interface (GSSAPI) authentication in the Pluggable Authentication Module (PAM) responder, cached connection state is freed upon completion without clearing the reference pointer. An attacker can exploit this by sending an additional request over the same connection, causing the service to access invalid memory and unexpectedly terminate. |
| CVE-2026-104032 | Medium | 2026-10-06 | Not applicable | Proof of concept only | A flaw was found in SSSD. An unprivileged local user can repeatedly request master automount map updates through the autofs responder due to missing authorization checks. This triggers global cache invalidation and forces repeated lookups to backend directory providers, leading to a Denial of Service (DoS) from degraded automount availability and elevated resource consumption. |
| CVE-2026-104031 | Medium | 2026-10-06 | Not applicable | No public exploit | A flaw was found in SSSD. In configurations where the autofs responder service is enabled, memory allocated during successful request processing is not released until the client connection terminates. A local attacker can exploit this vulnerability by maintaining an open connection and repeatedly submitting valid requests, leading to memory exhaustion and a Denial of Service (DoS). |
| CVE-2026-104030 | Medium | 2026-10-05 | Not applicable | No public exploit | A flaw was found in sssd. This vulnerability allows a local user to cause a Denial of Service (DoS) by submitting a specially crafted passkey authentication token that lacks null terminators. The authentication service reads past the end of the provided memory buffer, causing the process to crash and disrupting authentication services. |
| CVE-2026-104029 | Medium | 2026-10-05 | Not applicable | No public exploit | A flaw was found in SSSD. A local attacker can exploit this vulnerability by sending a specially crafted request to the autofs responder UNIX socket. Due to improper buffer offset calculation during request parsing, the service performs an out-of-bounds memory read. This flaw can cause the autofs responder process to crash, resulting in a denial of service (DoS). |
| CVE-2026-90462 | Medium | 2026-09-22 | Not applicable | Proof of concept only | A flaw was found in SSSD. When configured with the LDAP access provider and `ldap_access_order` including `ppolicy` or `lockout`, a fail-open condition in the LDAP ppolicy access check can occur if a user lookup returns zero results. This can incorrectly return success and cache an allow decision, permitting continued authorization for a deleted or deprovisioned user. A remote attacker with prior valid account context could exploit this to maintain access to information and potentially make limited modifications to resources that should no longer be available. |
| CVE-2026-25294 | High | 2026-09-17 | Not applicable | No public exploit | Transient DOS while parsing frame during channel usage. |
| CVE-2026-25280 | High | 2026-09-17 | Not applicable | No public exploit | Memory corruption when processing escape handling flow with insufficient user buffer sizes. |
| CVE-2026-25275 | High | 2026-09-17 | Not applicable | No public exploit | Transient DOS when processing authentication frames with invalid FILS information element header lengths. |
| CVE-2026-25261 | High | 2026-09-17 | Not applicable | No public exploit | Memory corruption while processing rear sensor IOCTL calls. |
| CVE-2026-24081 | High | 2026-09-17 | Not applicable | No public exploit | Transient DOS when processing a channel map with insufficient used channels and adaptive frequency hopping is fully enabled. |
| CVE-2026-24075 | High | 2026-09-17 | Not applicable | No public exploit | Memory Corruption when multiple threads issue concurrent IOCTL requests to the device control handler due to improper synchronization and race conditions. |
| CVE-2026-24074 | High | 2026-09-17 | Not applicable | No public exploit | Memory Corruption when processing data with large offset and length values exceeds buffer limits during data copy operations. |
| CVE-2025-59607 | High | 2026-09-17 | Not applicable | No public exploit | Memory Corruption when copying large input data exceeds normal allocation limits. |
| CVE-2026-90996 | Medium | 2026-09-14 | Not applicable | No public exploit | A flaw was found in sssd. A local unprivileged user could send a specially crafted request with a zero-length body to the Network Security Services (NSS) responder. This could lead to a denial-of-service condition, causing the NSS responder to become unstable or terminate. This vulnerability affects the availability of the system responder. |
| CVE-2026-90995 | Medium | 2026-09-14 | Not applicable | No public exploit | A flaw was found in SSSD (System Security Services Daemon). A local attacker with privileges to connect to the PAM (Pluggable Authentication Modules) responder socket can send a specially crafted protocol request. If the `pam_app_services` configuration is enabled and the service item is omitted from the request, a NULL pointer dereference can occur. This vulnerability leads to a denial of service, causing the PAM responder to crash and disrupt authentication services. |
| CVE-2026-65818 | Critical | 2026-09-03 | Not applicable | No public exploit | Server-side request forgery (ssrf) in Power Automate allows an authorized attacker to elevate privileges over a network. |
| CVE-2026-20320 | High | 2026-08-19 | Not applicable | Exploited | A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticated, remote attacker to read sensitive configuration information on an affected system. This vulnerability exists because XML entries are improperly parsed due to external entity resolution being allowed by default. An attacker could exploit this vulnerability by sending a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service. A successful exploit could allow the attacker to view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user. |
| CVE-2026-19617 | Medium | 2026-08-14 | Not applicable | No public exploit | A flaw was found in libdm. A local attacker could craft a malicious Logical Volume Manager (LVM) metadata configuration with deeply nested structures. This could lead to uncontrolled recursion in the libdm configuration file parser, exhausting the stack and causing any LVM command reading the metadata to crash. This vulnerability results in a Denial of Service (DoS) for affected systems. |
| CVE-2026-19548 | Medium | 2026-08-12 | Not applicable | No public exploit | Multiple Use-After-Free vulnerabilities were found in the add_archive_element function in ld/ldmain.c of the GNU linker (ld), a component of binutils. The root cause is that plugin_maybe_claim() in ld/plugin.c frees the original BFD object via bfd_close/_bfd_delete_bfd when entry->the_bfd->my_archive == NULL, but the caller retains both the original abfd parameter and a shallow copy (orig_input.the_bfd) as dangling pointers. These dangling pointers are subsequently dereferenced at three distinct locations in add_archive_element: 1. Line ~1442: accessing abfd->my_archive via bfd_usrdata(abfd->my_archive) 2. Line ~1493: multiple accesses to abfd and abfd->my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd->my_archive in trace/verbose logging The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd->my_archive == NULL, which is a valid state for standalone object files. Red Hat builds binutils with --enable-plugins and --enable-lto, confirming the vulnerable code path is compiled in and reachable. An attacker who can supply a crafted object or archive file to a build process using LTO-enabled linking could exploit this flaw to cause a denial of service (linker crash via segmentation fault). Arbitrary code execution is theoretically possible through heap manipulation but is substantially mitigated by hardening measures including stack protector, FORTIFY_SOURCE, ASLR, and PIE. The attack surface is limited to build-time environments — the linker is a development tool not exposed in production runtime. The most realistic exploitation scenario is a supply chain attack introducing a crafted object file as a build dependency in CI/CD pipelines or development environments. |
| CVE-2026-71227 | Medium | 2026-08-05 | Not applicable | No public exploit | A flaw was found in libkcapi. A local attacker can influence an application that uses the Asynchronous Input/Output (AIO) interface. By reusing an AIO-enabled handle after a prior completion error, the _kcapi_aio_read_all() function can enter a non-terminating wait loop. This can lead to a persistent denial of service, making the affected application or thread unresponsive. |
| CVE-2026-71226 | High | 2026-08-05 | Not applicable | No public exploit | Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers. |
| CVE-2026-71225 | Medium | 2026-08-05 | Not applicable | No public exploit | A flaw was found in libkcapi. When performing one-shot symmetric cipher operations on large inputs (over 64 KiB) in stateful modes such as Counter (CTR) or Cipher Block Chaining (CBC), the library improperly reuses the Initialization Vector (IV) for each internal data chunk. A remote attacker could potentially exploit this by making an application that uses libkcapi process specially crafted large inputs. This can lead to a significant weakening of data confidentiality, as the repeated IV use can expose relationships in encrypted plaintext, and may also affect data integrity by causing incorrect cryptographic processing. |
| CVE-2026-68744 | Low | 2026-08-04 | Not applicable | No public exploit | A flaw was found in SSSD. The sss_nss_protocol_fill_initgr() function in the NSS responder pre-allocates reply space for all group entries but does not shrink the packet when groups are skipped, causing uninitialized heap bytes to be transmitted to the client. A local attacker can exploit this to disclose cached directory data and heap layout information from the sssd_nss process. |
| CVE-2026-68743 | High | 2026-08-04 | Not applicable | No public exploit | A flaw was found in SSSD. The extract_authtok_v1() function in the PAM responder does not validate the auth_token_length field against the remaining buffer size before processing. A local attacker can exploit this via a crafted protocol v1 request to the PAM responder socket, causing an out-of-bounds read and process crash, resulting in a denial of service. |
| CVE-2026-25292 | High | 2026-08-04 | Not applicable | No public exploit | Memory Corruption when processing untrusted user input in the fastboot command handler for audio framework configuration. |
| CVE-2026-25289 | Critical | 2026-08-04 | Not applicable | No public exploit | Memory Corruption when processing Device Capability Extended attributes in certain NAN Service Discovery Frames with invalid length values. |
| CVE-2026-25288 | High | 2026-08-04 | Not applicable | No public exploit | Transient DOS when processing a short target wake time channel usage response frame with insufficient packet size. |
| CVE-2026-24084 | High | 2026-08-04 | Not applicable | No public exploit | Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities. |
| CVE-2026-24079 | High | 2026-08-04 | Not applicable | No public exploit | Cryptographic Issue while processing registration requests with malformed or missing authentication parameters. |
| 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-2026-24076 | Medium | 2026-08-04 | Not applicable | No public exploit | Memory Corruption when processing registry values with incorrect types using a direct query method. |
| CVE-2026-68742 | Medium | 2026-08-03 | Not applicable | No public exploit | A flaw was found in SSSD. The sss_nss_protocol_parse_addr() function in the NSS responder does not validate the addrlen field against the remaining packet body size. A local attacker can exploit this via a crafted GETHOSTBYADDR request to the NSS responder socket, causing an out-of-bounds read and process crash, resulting in a denial of service. |
| CVE-2026-18508 | Medium | 2026-08-03 | Not applicable | No public exploit | A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction. |
| CVE-2026-18477 | Medium | 2026-08-03 | Not applicable | No public exploit | A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue. |
| CVE-2026-20298 | Medium | 2026-07-15 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.3.2512.15, 10.2.2510.18, and 10.1.2507.24, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could view stored credential hashes when they access the `/servicesNS/-/-/storage/passwords` REST endpoint through the `|rest` Search Processing Language (SPL) command.<br><br>The exposure happens because the `|rest` SPL command returns the `encr_password` field in the results of the `/servicesNS/-/-/storage/passwords` REST endpoint. |
| CVE-2026-20297 | High | 2026-07-15 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, and 9.3.14, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, and 10.1.2507.24, a user who holds a role that contains the `edit_local_apps` and `install_apps` capabilities could cause a legitimate app installation to write files outside the intended app directory, into `$SPLUNK_HOME/etc/` and its subdirectories.<br><br>The vulnerability is caused by a path traversal in the app installation workflow, which does not restrict the installation path to the intended app directory. |
| CVE-2026-20296 | High | 2026-07-15 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, and 10.1.2507.24, an attacker could trick a user that holds a role with the `list_deployment_server` capability into running arbitrary Search Processing Language (SPL) searches on their behalf as `splunk-system-user`, allowing for access to stored credentials and indexed data.<br><br>The vulnerability is possible because Deployment Server endpoints in Splunk Web do not validate Cross-Site Request Forgery (CSRF) tokens on GET requests, and caller-supplied input is not correctly neutralized before it is placed into an SPL search. |
| CVE-2026-1563 | Medium | 2026-07-15 | Not applicable | No public exploit | Pega Platform versions 8.1.0 through 25.1.2 are affected by an Reflected Cross-site scripting (XSS) vulnerability in a user interface component. Requires a high privileged user with a developer role. |
| CVE-2026-1562 | Medium | 2026-07-15 | Not applicable | No public exploit | Pega Platform versions 8.1.0 through 25.1.2 are affected by an Stored Cross-site scripting (XSS) vulnerability in a user interface component. Requires a high privileged user with a developer role. |
| CVE-2026-60114 | High | 2026-07-14 | Not applicable | Proof of concept only | Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a path traversal vulnerability that allows attackers with access to the restore functionality to write files to arbitrary locations by uploading crafted JSON backup files with unvalidated keys used to construct file paths. Attackers can exploit the lack of key validation in the JSON restore process, combined with the absence of a required passphrase in the default configuration or the default passphrase 'opendoor', to write arbitrary JSON files outside the intended data directory. |
| CVE-2026-58479 | Critical | 2026-07-14 | Not applicable | Proof of concept only | Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a command injection vulnerability in the optional cli_control plugin that allows unauthenticated or cross-site request forgery attackers to execute arbitrary operating-system commands by storing a malicious payload via the plugin's HTTP endpoint. Attackers can trigger execution by activating the associated irrigation station, exploiting the absence of passphrase protection or the default passphrase 'opendoor', to achieve arbitrary command execution on the underlying host. |
| CVE-2026-58478 | Medium | 2026-07-14 | Not applicable | Proof of concept only | Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a server-side request forgery (SSRF) vulnerability that allows unauthenticated attackers to make the device issue arbitrary HTTP requests by supplying a malicious callback URL when the optional Node-RED plugin is installed. Attackers can exploit the lack of destination validation and the default passphrase 'opendoor' to send blind HTTP requests to arbitrary internal or external hosts not otherwise directly accessible. |
| CVE-2026-58477 | High | 2026-07-14 | Not applicable | Proof of concept only | Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a mass assignment vulnerability that allows unauthenticated attackers to overwrite sensitive configuration settings by supplying arbitrary parameter names in HTTP requests. Attackers can manipulate parameters corresponding to sensitive values such as the passphrase and listening port, and can also achieve the same result through cross-site request forgery due to the absence of adequate request validation. |
| CVE-2026-58476 | High | 2026-07-14 | Not applicable | Proof of concept only | Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a cross-site request forgery vulnerability that allows remote attackers to perform state-changing administrative actions by luring a logged-in administrator into visiting a malicious page that issues HTTP GET requests without CSRF token validation or origin verification. Attackers can trigger actions such as disabling the passphrase, rebooting the device, deleting programs, or installing plugins, with the default configuration exposing these endpoints to unauthenticated users due to no required passphrase and a default credential of 'opendoor'. |
| CVE-2026-58475 | Medium | 2026-07-14 | Not applicable | No public exploit | Sustainable Irrigation Platform (SIP) through version 5.2.16 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject arbitrary JavaScript by supplying malicious script payloads within program names submitted via HTTP requests. Attackers can exploit the lack of output encoding on rendered program names to execute arbitrary JavaScript in the browsers of any users viewing the affected page, with exploitation facilitated by the absence of a required passphrase or the default passphrase 'opendoor'. |
| CVE-2026-25268 | High | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when processing invalid HT40 channel layouts during dynamic channel switching operations. |
| CVE-2026-21384 | Medium | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when updating prepared commands with invalid port indices based on user space input exceeds supported read client limits. |
| CVE-2026-21383 | High | 2026-07-06 | Not applicable | No public exploit | Cryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security. |
| CVE-2026-21379 | High | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when allocating memory with sizes that exceed the maximum allowed value. |
| CVE-2026-21370 | Medium | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values. |
| CVE-2026-21369 | Medium | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when handling flash commands due to outdated LED count values being used after userspace modification. |
| CVE-2026-21368 | Medium | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when parsing jpeg commands due to unaccounted extra writes to the buffer during validation checks. |
| CVE-2025-59617 | High | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input. |
| CVE-2025-59616 | High | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when processing multiple IOCTL calls with the same buffer file descriptor input due to accessing already freed memory. |
| CVE-2025-59615 | High | 2026-07-06 | Not applicable | No public exploit | Memory Corruption when invoking device input/output control operations for mapping and unmapping persistent memory buffers due to improper synchronization. |
| CVE-2026-13757 | Medium | 2026-06-29 | Not applicable | No public exploit | A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services. |
| CVE-2026-13595 | Medium | 2026-06-29 | Not applicable | No public exploit | A flaw was found in the libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service. |
| CVE-2026-55653 | Medium | 2026-06-23 | Not applicable | No public exploit | A flaw was found in OpenSSH. A malicious SSH server can exploit a double free vulnerability in the Diffie-Hellman Group Exchange (DH-GEX) client path. This occurs during FIPS (Federal Information Processing Standards) mode known-group validation when the client processes attacker-controlled DH-GEX group parameters. Successful exploitation leads to client-side process termination, resulting in a Denial of Service (DoS). |
| CVE-2026-54100 | High | 2026-06-22 | Not applicable | No public exploit | A flaw was found in the Windows Machine Config Operator (WMCO) for Red Hat OpenShift Container Platform. WMCO establishes SSH connections to Windows worker nodes without verifying the remote server host key. An adjacent-network attacker who can intercept or redirect WMCO's SSH session can capture WICD and kubelet bootstrap credentials transferred during node configuration, enabling compromise of Windows node identities in the cluster. |
| CVE-2026-54099 | High | 2026-06-22 | Not applicable | No public exploit | A flaw was found in the Windows Machine Config Operator (WMCO) for Red Hat OpenShift Container Platform. The WICD CSR auto-approver validates that a Certificate Signing Request contains the organization system:wicd-nodes but does not reject additional organization values such as system:masters. A compromised Windows worker node that holds WICD credentials can submit a CSR that is auto-approved and signed by the cluster, yielding a client certificate that grants cluster-administrator privileges and enabling full cluster takeover. |
| CVE-2026-12725 | Medium | 2026-06-22 | Not applicable | No public exploit | A heap-based buffer overflow was found in dnsmasq. When DNSSEC validation and query logging are both enabled, logging of DS or DNSKEY replies containing unsupported algorithm or digest types can cause dnsmasq to write past the end of an internal logging buffer. A remote attacker able to supply such a DNS response may crash the dnsmasq process, resulting in denial of service. |
| CVE-2026-11372 | Medium | 2026-06-22 | Not applicable | No public exploit | IBM TRIRIGA Application Platform 5.0.2 through 5.0.3 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-44495 | High | 2026-06-11 | Not applicable | Proof of concept only | Axios is a promise based HTTP client for the browser and Node.js. From 0.19.0 to before 0.31.1 and 1.15.2, Axios contains prototype-pollution gadgets in request config processing. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator. Axios does not itself create the prototype pollution. Exploitability requires a separate prototype-pollution vulnerability or equivalent attacker control over Object.prototype before Axios creates a request. This vulnerability is fixed in 0.31.1 and 1.15.2. |
| CVE-2026-46625 | High | 2026-06-10 | Not applicable | Proof of concept only | JavaScript Cookie is a JavaScript API for handling cookies, client-side. Prior to version 3.0.7, js-cookie's internal assign() helper copies properties with for...in + plain assignment. When the source object is produced by JSON.parse, the JSON object's "__proto__" member is an own enumerable property, so the for…in enumerates it and the target[key] = source[key] write triggers the Object.prototype.__proto__ setter on the fresh target ({}). The result is a per-instance prototype hijack: Object.prototype itself is untouched, but the merged attributes object now inherits attacker-controlled keys. Because the consuming set() function then enumerates the merged object with another for...in, every key the attacker placed on the polluted prototype lands in the resulting Set-Cookie string as an attribute pair. The attacker can set domain=, secure=, samesite=, expires=, and path= on cookies whose attributes the developer thought were locked down. This issue has been patched in version 3.0.7. |
| CVE-2026-20259 | Medium | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4 and 10.0.7, and Splunk Cloud Platform versions below 10.4.2604.0, 10.3.2512.12, 10.2.2510.15, 10.1.2507.23, 10.0.2503.14, and 9.3.2411.131, a user who holds a Splunk role that contains the high-privilege capability `edit_saved_search_owner` could reassign saved search ownership to users outside their authorized scope. The ownership reassignment endpoint lacks access control. |
| CVE-2026-20258 | High | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.11, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could store a malicious script in a classic dashboard HTML panel, causing unauthorized JavaScript code to execute in the browser of another user. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will. |
| CVE-2026-20257 | Medium | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a classic dashboard that exfiltrates sensitive data from the browser of a higher-privileged user who views it. The exfiltration is possible because classic dashboard panels do not fully validate style attribute values, which can allow for requests to reach external domains outside the configured Trusted Domains List. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will. |
| CVE-2026-20256 | Medium | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could cause data exfiltration through classic dashboards by redirecting a victim to an external site using a protocol-relative URL in a drill-down link.<br><br>The vulnerability exists because the URL classifier in classic dashboards only recognizes `http://` and `https://` schemes when checking for external URLs. Protocol-relative URLs such as `//attacker.com` bypass this check entirely, and Splunk Web does not show the external-navigation warning dialog to the victim. |
| CVE-2026-20255 | Medium | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious classic dashboard that exfiltrates sensitive data to an external server. The vulnerability exists because URL validation on the external content dialog is incomplete, which can allow for requests to untrusted domains when a user interacts with a crafted dashboard. |
| CVE-2026-20254 | Medium | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could craft a malicious classic dashboard that exfiltrates sensitive data to an external server when a higher-privileged user views it, bypassing the external content restriction through a Cascading Style Sheets (CSS) injection.<br><br>The Trusted Domains security check does not fully validate inline style attribute values, which can allow for outbound requests to untrusted domains and credential exfiltration when a victim views a crafted dashboard. |
| CVE-2026-20252 | High | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could send server-side requests to arbitrary internal destinations through the Dashboard Studio PDF export feature. The vulnerability exists because the trusted-domain validation uses a prefix match that can be bypassed with attacker-controlled subdomains (for example, docs.splunk.com.evil.com), and because the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist. |
| CVE-2026-20251 | High | 2026-06-10 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, Splunk Cloud Platform versions below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, and Splunk Secure Gateway versions below 3.10.6, 3.9.20, and 3.8.67, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could perform a Remote Code Execution (RCE) through the Splunk Secure Gateway app.<br><br>The Remote Code Execution is possible because of unsafe deserialization of App Key Value Store (KV Store) data through the ‘jsonpickle’ Python library, which reconstructs arbitrary Python objects from specially crafted JavaScript Object Notation (JSON) without adequate validation. |
| CVE-2026-41724 | High | 2026-06-08 | Not applicable | No public exploit | VMware Cloud Foundation Operations contains multiple stored cross-site scripting vulnerabilities.A malicious actor with privileges to create policies, views or text-widgets may be able to inject scripts to perform administrative actions in VMware Cloud Foundation Operations. |
| CVE-2026-41723 | High | 2026-06-08 | Not applicable | No public exploit | VMware Cloud Foundation Operations contains multiple stored cross-site scripting vulnerabilities.A malicious actor with privileges to create policies, views or text-widgets may be able to inject scripts to perform administrative actions in VMware Cloud Foundation Operations. |
| CVE-2026-41722 | High | 2026-06-08 | Not applicable | No public exploit | VMware Cloud Foundation Operations contains multiple stored cross-site scripting vulnerabilities.A malicious actor with privileges to create policies, views or text-widgets may be able to inject scripts to perform administrative actions in VMware Cloud Foundation Operations. |
| CVE-2026-1784 | High | 2026-06-02 | Not applicable | No public exploit | The Route OpenShift resource allows to define routes to make pods reachable at a subdomain through HAProxy. It was found that the checks performed on the spec.path YAML stanza in a Route document was insufficient and could allow a controlled injection of the HAProxy configuration. |
| CVE-2026-25277 | High | 2026-06-01 | Not applicable | No public exploit | Memory corruption while using Strongbox due to buffer overflow. |
| CVE-2026-25276 | High | 2026-06-01 | Not applicable | No public exploit | Memory corruption while using Strongbox due to missing bounds check. |
| CVE-2026-25260 | High | 2026-06-01 | Not applicable | No public exploit | Memory Corruption when accessing shared buffers without validation of concurrent user-mode input modifications. |