In the Linux kernel, the following vulnerability has been resolved: HID: ft260: fix stack-use-after-return write in I2C read race ft260_i2c_read() points dev->read_buf at a caller-supplied buffer (often an on-stack variable), arms a completion and waits up to five seconds for the device to return the data. The HID input callback ft260_raw_event() runs in the input/IRQ path, independent of the dev->lock mutex held by the read path, and copies the device-supplied payload into dev->read_buf after a plain NULL check. These two paths share read_buf, read_idx and read_len with no serialization. If the device delays its response until the read times out, ft260_i2c_read() resets the controller, clears read_buf and returns, unwinding the stack frame the buffer lived in. A response that arrives at that moment lets ft260_raw_event() pass the NULL check and then memcpy() the device-controlled payload into the now-freed stack location, a bounded but attacker-influenced stack-use-after-return write triggerable by malicious or malfunctioning hardware. Add a dedicated spinlock that serializes every access to read_buf, read_idx and read_len. ft260_raw_event() now holds it across the NULL check, the memcpy and the index update, while the read path takes it when arming and when clearing the buffer, so the teardown can no longer slip between the check and the copy.
In the Linux kernel, the following vulnerability has been resolved: nilfs2: reject invalid block index in GC ioctl Syzbot reported list corruption caused by a double list_add_tail() call on bh->b_assoc_buffers within nilfs_lookup_dirty_data_buffers(). Analysis revealed that the root cause was the insertion of a page/folio with a page index of ULONG_MAX into the page cache via the GC ioctl. filemap_get_folios_tag(), called by nilfs_lookup_dirty_data_buffers(), repeatedly detects a dirty folio with a page index of ULONG_MAX due to index wrap-around, leading to duplicate processing of dirty buffers. As a preparatory step, the GC ioctl loads the page/folio of the block to be moved during GC and inserts it into the page cache based on information in the nilfs_vdesc structure passed as an argument. Normally, this does not cause issues because the user-space GC library configures the nilfs_vdesc structure properly. However, since there is no range check on the parameters determining the page index, a request with artificially crafted parameters -- such as those generated by Syzbot -- can result in a page/folio being inserted with a page index of ULONG_MAX, triggering the above problem. This resolves the issue by checking the ranges of 'vd_offset' and 'vd_vblocknr' in the nilfs_vdesc structure that determine the page index, thereby preventing the invalid page/folio insertions.
Chroma 1.5.9 fails to validate maximum bounds on HNSW index parameters max_neighbors, ef_construction, and ef_search in collection-create requests. Unauthenticated attackers can supply arbitrarily large parameter values to exhaust server memory and cause denial of service during index compaction.
The Frontend Admin by DynamiApps WordPress plugin before 3.29.13 does not properly validate a user-controllable directory path before deleting files within it, allowing unauthenticated attackers to delete index.php and .htaccess files outside the intended directory, including the WordPress root, which can render the site inoperable. Successful exploitation requires a non-default form configuration.
The tailwind-scrollbar-styles npm package version 4.0.3 contains malicious code embedded in its dist/index.js file. This code executes a base64-encoded payload that queries Ethereum RPC endpoints to retrieve a transaction from a hardcoded Ethereum address. It decodes part of the transaction to obtain a command-and-control (C2) server IP address, fetches and XOR-decodes commands from that server, and executes them via eval and a detached Node.js process. After execution, the malicious code removes itself from the file to evade detection and forensic analysis. This mechanism allows the attacker to dynamically rotate the C2 server by publishing new Ethereum transactions. No patch or remediation information is provided.
The npm package @bx-ui-framework/common versions 1.2.0 and 15.0.0 declare a self-referential dependency with a URL pointing to an external repository (https://repo.remoteknight.com/bx-ui-framework/common) instead of a version range. This causes npm to fetch and install code from that URL during installation, executing any lifecycle scripts it contains. The package's shipped index.js is inert, making the dependency declaration the primary attack vector. Whoever controls the external repository can execute arbitrary code on any machine installing the package, exploiting a dependency confusion technique.
A vulnerability was identified in itsourcecode Online Medicine Delivery System 1.0. Impacted is an unknown function of the file /index.php?q=orderdetails. Such manipulation of the argument location leads to cross site scripting. The attack may be launched remotely. The exploit is publicly available and might be used.
SciPhi-AI R2R versions up to 3.6.6 and version 0 are affected by a critical stacked SQL injection vulnerability. This flaw allows unauthenticated attackers to execute arbitrary SQL commands by manipulating the index name parameter in the vector index creation endpoint. The vulnerability arises because the index name is directly interpolated into a CREATE INDEX SQL statement without proper quoting or validation, enabling execution of arbitrary DDL and DML statements under the PostgreSQL superuser account.
A vulnerability was detected in SeaCMS up to 13.6. Affected is the function addslashes of the file weixin/index.php of the component WeChat Module. The manipulation of the argument Content results in sql injection. The attack may be launched remotely. The exploit is now public and may be used.
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix bandwidth group reservation indexing Valid bandwidth group IDs range from 1 through MAX_GROUPS, while Group ID 0 is reserved. tb_consumed_dp_bandwidth() uses the Group ID directly to index its local group_reserved[] array. The array currently has MAX_GROUPS entries, so its valid indices are 0 through MAX_GROUPS - 1. Group ID MAX_GROUPS therefore accesses one element past the end, and the final group's reserved bandwidth is not included when the array is summed. Give group_reserved[] MAX_GROUPS + 1 entries so direct Group ID indexing covers the reserved ID 0 and valid IDs 1 through MAX_GROUPS.
CVE-2026-71220 is a stack out-of-bounds write vulnerability in the gfs2-utils package on Red Hat Enterprise Linux 7. The flaw occurs in the gfs2_edit tool where the di_height field from on-disk inode metadata is used as an array index without bounds checking, leading to a stack buffer overflow. This vulnerability may allow an attacker with local access and user interaction to execute arbitrary code by processing crafted GFS2 filesystem images. The kernel GFS2 driver is not affected. Exploitation requires an administrator to run gfs2_edit on a malicious image. Mitigations include avoiding running gfs2_edit on untrusted images and using container or VM isolation. No official fix version is stated yet.
A vulnerability has been found in NousResearch hermes-agent 0.18.0. This affects the function fetchLinkTitle of the file apps/desktop/src/app/artifacts/index.tsx of the component Link Title Fetch. Such manipulation of the argument url leads to server-side request forgery. The attack can be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.
WWBN AVideo contains a broken access control vulnerability in the unauthenticated feed/index.php endpoint that disables per-video visibility checks when a program_id parameter is supplied. Attackers can enumerate playlist identifiers and retrieve unlisted and group-restricted videos by requesting the RSS feed with any visible playlist id, including empty playlists that return the entire site's hidden video catalogue.
The npm package 'btree-time-index' version 1.2.1 contains malicious code or depends on a package with malicious code. Installation or use of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different machine. Removal of the package does not guarantee complete eradication of the malicious software introduced.
The npm package 'ordered-kv-index' version 1.0.1 contains malicious code or depends on a package with malicious code. Installing or running this package can fully compromise the affected computer, potentially exposing all stored secrets and keys. Removal of the package does not guarantee elimination of all malicious software introduced. Immediate rotation of all secrets and keys from a separate, uncompromised system is strongly advised.
SQL injection vulnerability in the endpoint /ocsreports/index.php?function=admin_double due to improper processing of the values in the ID field included in the selected_grp_dupli[] parameter. An authenticated user with operator privileges can manipulate these values to alter the SQL queries executed by the application and retrieve information stored in the database.
Boruta is a standalone authorization server that aims to implement OAuth 2.0 and Openid Connect up to decentralized identity specifications. Prior to version 0.10.0, BorutaIdentityWeb.UserSettingsController.update/2 atomizes every key of the user-supplied request body via String.to_atom/1 before any validation. Because String.to_atom interns atoms permanently in the BEAM atom table (default cap 1,048,576 atoms; ERL_MAX_ATOMS), any authenticated end user can send PUT /users/settings with a user[<fresh-key>]=... body containing fresh keys per request and exhaust the global VM atom table. Once the table is full, the BEAM aborts with no more index entries in atom_tab and the entire OIDC server (auth, admin, gateway apps in the umbrella) crashes. The route is protected only by require_authenticated_user and a per-IP rate limit of 10 requests/second; a logged-in end user can hit it. The keys are atomized unconditionally before the downstream Accounts.update_user/6 call, so even failing updates contribute to exhaustion. This issue has been patched in version 0.10.0.
NLTK version 3.9.4 contains a path traversal vulnerability in its FrameNet and NKJP corpus readers. This flaw allows parsing of XML files outside the trusted corpus root by using unsafe selectors or poisoned index state. The issue is fixed in version 3.10.0, which enforces path-safety checks to prevent outside-root XML parsing.
Baserow version 2.3.3 contains a SQL injection vulnerability in its index() formula function. A low-privileged authenticated user who can create or modify formula fields can exploit this by providing an undocumented fourth argument that is directly interpolated into a PostgreSQL expression. This causes the injected SQL to execute with the privileges of the Baserow PostgreSQL role, which is higher than the user's application permissions. This vulnerability is identified as CVE-2026-19754 and is classified as high severity.