An out-of-bounds read vulnerability in the ZRLE decoder of GlavSoft TightVNC Viewer for Windows before 2.8.88 allows a malicious or compromised VNC server to read heap memory beyond the palette allocation and crash the viewer by sending ZRLE-encoded tiles whose palette indices exceed the declared palette size. readPaletteRleTile() and readPackedPaletteTile() use the attacker-supplied index to look up colours without validating it against the palette size; out-of-bounds heap data is copied into the framebuffer (garbled display) or the read faults, terminating the viewer.
An out-of-bounds memory read vulnerability exists in the web management daemon of Brocade Fabric OS versions before 10.0.1. Unauthenticated HTTP endpoints process specific URL query parameters without validating array index boundaries or performing numerical range checks. An unauthenticated remote attacker can exploit this issue by sending a single, crafted HTTP request containing extreme numerical values in the query string. This causes an invalid memory dereference, resulting in a crash of the web management process (Denial of Service) and potential temporary management-plane disruption.
CVE-2026-76279 is a vulnerability in Splunk Enterprise versions prior to 10.4.3, 10.2.7, 10.0.10, and 9.4.15. It allows users with the run_collect capability to write events to internal indexes beyond their configured index access. This occurs because Splunk Enterprise does not normalize whitespace in index names before enforcing index-access restrictions. The vulnerability has a medium severity with a CVSS score of 4.3.
CVE-2026-76273 is a medium severity vulnerability in Splunk Enterprise that affects versions prior to 10.4.3, 10.2.7, 10.0.10, and 9.4.15. It allows a user with the run_collect capability to use the collect SPL command to insert attacker-controlled content into system-level messages due to improper validation of the index name. This could affect the control or data flow within the Splunk platform instance.
CVE-2026-107221 is an out-of-bounds write vulnerability in the qax-os excelize library affecting versions from 2.0.0 up to and including 2.11.0. The flaw occurs in the checkRow function when processing spreadsheet rows with cells that are not sorted by column in the XML, causing an index out of range panic and process crash. This affects worksheet API calls such as GetCellValue, GetCellFormula, CalcCellValue, GetMergeCells, and SetCellValue. The vulnerability leads to an unauthenticated denial of service via a deterministic panic. A fix involves correcting the sizing of internal data structures to handle unordered cells properly.
CVE-2026-107218 is a medium severity vulnerability in the Go library excelize (versions 2.10.1 through 2.11.0) used for reading and writing Microsoft Excel spreadsheets. The issue arises from improper validation of array indices in the RIGHT function, which inconsistently uses UTF-16 code-unit counts and Unicode code-point counts when slicing strings. This mismatch can cause a negative index panic during formula evaluation when processing supplementary-plane Unicode characters. No fix is currently available for this vulnerability.
CVE-2026-107217 is an integer overflow vulnerability in the Excelize Go library used for reading and writing Microsoft Excel spreadsheets. The function ColumnNameToNumber does not detect overflow when converting long column names to numeric indices, causing a wraparound to zero. This leads to a negative slice index during worksheet normalization, which can cause the application to panic and terminate unexpectedly. No fixed version is currently available.
CVE-2026-107211 is a high-severity vulnerability in the qax-os excelize library involving improper validation of array indices when processing pivot tables in .xlsx files. The vulnerability arises because the library indexes arrays with attacker-controlled integers from pivot table XML parts without bounds checking, leading to runtime panics (index out of range errors). This can cause the host process to crash when opening crafted malicious Excel files containing pivot tables. The issue affects versions from 2.8.1 through 2.11.0. No official patch or fix is currently documented.
A heap buffer overflow vulnerability exists in NTFS-3G versions before 2026.7.7 in the ntfs_ib_copy_tail() function within libntfs-3g/index.c. This flaw allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image and triggering the overflow through directory extension operations such as file creation. The vulnerability has a high severity rating with a CVSS score of 7.7.
A heap buffer overflow vulnerability exists in NTFS-3G versions before 2026.7.7 in the ntfs_ir_to_ib() function within index.c. This flaw can be triggered by extending a directory, such as creating a file, using a crafted malicious NTFS image. The vulnerability affects the SUID-root ntfs-3g binary and allows an attacker to corrupt heap memory.
A heap buffer overflow vulnerability exists in NTFS-3G versions before 2026.7.7 in the ntfs_ib_cut_tail() function within libntfs-3g/index.c. This flaw allows an attacker to corrupt heap memory by crafting a malicious NTFS image and creating a file in a specially crafted directory. The vulnerability affects the SUID-root ntfs-3g binary, potentially leading to high impact on confidentiality, integrity, and availability.
CVE-2026-103009 is a high-severity authorization bypass vulnerability in Elasticsearch affecting versions 8.13.0 through 8.19.22, 9.0.0 through 9.4.7, and 9.5.0 through 9.5.4. It involves the Remote Cluster Security 2.0 model where a cross-cluster search request can be crafted to bypass authorization checks by using mismatched shard identifiers. This allows an attacker with a cross-cluster API key authorized for one index to access documents, field mappings, and metadata of an unauthorized index, and in limited cases modify retention-lease state. The vulnerability has a CVSS score of 7.1 and no known exploits in the wild have been reported. Patch status is not confirmed from the provided data.
CVE-2026-103006 is an uncontrolled recursion vulnerability in Elasticsearch's search aggregation feature. An authenticated user with read access to an index can submit a deeply nested aggregation request that triggers unbounded recursion. This leads to resource exhaustion and causes the affected node to terminate and require manual recovery. The vulnerability affects multiple versions of Elasticsearch from 8.0.0 through 8.19.20, 9.0.0 through 9.4.5, and 9.5.0 through 9.5.1. The CVSS score is 6.5, indicating medium severity.
CVE-2026-102408 is a medium severity vulnerability in Elastic Elasticsearch involving inefficient regular expression complexity. The ES|QL CHUNK function accepts user-supplied regular expressions without validating their computational complexity or bounding execution time. An authenticated user with read access to any text-based index can submit crafted regex patterns that cause catastrophic backtracking, leading to excessive CPU consumption and degraded query throughput on affected nodes. The issue results in denial of service conditions but does not crash the cluster.
Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0, renderSSRError() in utils/render-ssr-error/src/index.js used diagnostic data from utils/render-ssr-error/src/env.js to serialize process.env, request headers, and cookies into the HTTP page returned by serve.devError(), while the development server listened on all interfaces by default. Any network-adjacent client that reaches an SSR or SSG render failure through this development-only error path can obtain shell environment secrets. The renderer escaped only one exact lowercase script closing-tag spelling, so case variants and valid closing-tag delimiter variants in reflected diagnostic data could terminate the script element and inject markup; executing the injected code in a developer browser additionally requires the payload to accompany that developer's request. This issue is fixed in @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0.
A security update addresses CVE-2026-63209, a signed integer overflow vulnerability in the github.com/klauspost/compress library's s2.NewDict() function. This flaw allows an attacker to bypass repeat index validation and cause a process crash. The issue was identified by the SUSE Product Security Team and affects SUSE distributions. No specific affected versions or patch details are provided.
A vulnerability in the Linux kernel's SCPI clock driver allows an out-of-range DVFS index to be used due to missing upper bound checks. This can cause the driver to treat invalid data as a clock rate, potentially leading to out-of-bounds memory access or incorrect frequency reporting. The issue arises if the SCP firmware is buggy or returns stale values. The flaw has been fixed by adding proper upper bound validation.
An off-by-one bounds check vulnerability in the Bluetooth btintel_pcie driver in the Linux kernel allows an out-of-bounds array access. The issue occurs because the check incorrectly permits an index equal to the array count, leading to a potential out-of-range access. This flaw has been fixed by changing the bounds check to reject all out-of-range indices.
A vulnerability in the Linux kernel's wwan t7xx driver allows out-of-bounds array access due to improper validation of the netif index in the t7xx_ccmni_recv_skb() function. The netif index is five bits wide but the array ccmni_inst[] only has 21 entries, leading to potential out-of-bounds reads when indexes 21 to 31 are used. This causes the driver to dereference invalid memory from a callback table, which can lead to undefined behavior. The issue is fixed by adding a bounds check that drops packets with out-of-range indexes.
CVE-2026-98237 is a vulnerability in the Linux kernel's mhi_wwan_mbim driver where a cyclic Neighbor Discovery Protocol (NDP) chain can cause an infinite loop in the mhi_mbim_rx() function. This occurs because the NDP traversal only stops when the next NDP index is zero, but a modem can point an NDP at itself or an earlier NDP, causing the loop to spin indefinitely on one CPU. The fix adds a check to break the loop when the next NDP offset is not larger than the current one, preventing CPU exhaustion.