Etherpad is a real-time collaborative editor. From 1.8.14 until 3.3.3, the pre-authentication /static/* plugin asset handler in src/node/utils/Minify.ts performs a backslash-to-forward-slash conversion after src/node/utils/sanitizePathname.ts has completed its POSIX path checks. On POSIX systems the sanitizer correctly treats backslashes as ordinary filename bytes, but the later conversion turns encoded backslash-separated parent-directory segments into traversal components without revalidation or containment. The expressPreSession registration and the always-present ep_etherpad-lite core pseudo-plugin make this path reachable without credentials, allowing a remote attacker to read any file available to the Etherpad process. Disclosed configuration or environment secrets can expose administrator credentials, after which the administrator plugin installer can provide in-process code execution and full server compromise. This issue is fixed in version 3.3.3.
CVE-2026-77312 is a critical path traversal vulnerability in flytohub's flyto-core execution kernel for automation and AI-agent workflows. Versions prior to 2.26.8 fail to properly confine certain file-writing modules within the sandbox directory, allowing attacker-controlled paths to write files outside the intended boundary. This can lead to overwriting critical application files and potentially achieving code execution on the host. The issue is fixed in version 2.26.8.
CVE-2026-77314 is a path traversal vulnerability in flytohub's flyto-core prior to version 2.26.8. The vulnerability allows an attacker with limited privileges to specify a crafted recipe_name that causes the system to load and execute YAML workflows outside the intended recipe directory. Although this does not grant unrestricted code execution, it enables unintended execution of allowed modules related to browser, network, file, and data processing. The issue is fixed in version 2.26.8.
In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user could also run internal Search Processing Language (SPL) commands and bypass SPL safeguards for risky commands within indexes that the role can search.
The vulnerability is possible because Splunk Enterprise does not correctly escape required field values before it includes them in an internally generated search.
For more information, see Search endpoint descriptions (https://help.splunk.com/en/splunk-enterprise/rest-api-reference/9.4/search-endpoints/search-endpoint-descriptions), authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.5-configuration-file-reference/authorize.conf), and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands).
CVE-2026-83631 is a vulnerability in Okta Verify for macOS affecting Intel-based systems. The Okta Device Access component configures a LaunchDaemon service whose program path resolves through a symbolic link in /usr/local/bin. If local non-root users have write access to this path due to non-standard directory permissions, they can modify the symbolic link target. This allows execution of a replacement binary when the LaunchDaemon service restarts. The issue is fixed in version 9.75.1.
A path traversal vulnerability (CWE-22) exists in baserCMS versions 5.2.3 through 5.2.x in the BcThemeFileService::getFullpath() function. This flaw allows an authenticated administrator to bypass path containment checks when realpath() fails on a nonexistent theme subdirectory, enabling access to files outside the intended theme directory. Exploitation can lead to file writes, overwrites, or deletions within the PHP process permissions and potentially remote code execution if executable PHP files are written. The issue is fixed in version 5.3.0.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use the Automation Dependency Wheel Representational State Transfer (REST) API to write arbitrary files outside the intended directory, which could lead to arbitrary code execution.
The vulnerability is possible because Splunk SOAR does not restrict uploaded automation dependency wheel filenames to the intended storage directory.
In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_admin" Splunk Enterprise Security role could execute arbitrary code on the search head as the user account running Splunk Enterprise by combining lookup file upload and Configuration Checker functionality.
The vulnerability is possible because Splunk Enterprise Security does not restrict lookup upload file types or keep Configuration Checker module paths within the intended directory.
For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation.
CVE-2026-131191 is a vulnerability in Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.17 that allows non-admin and non-power users to read private index configuration values of other users via the deployment server REST API. This occurs because the API does not restrict repository location inputs to configured deployment repositories before accessing indexes.conf stanzas.
Joomla Extension - vi-solutions - Arbitrary file write leading to remote code execution in CSS editor in Visforms extension 1.0.0-5.6.3, 6.0.0-6.2.0 - The CSS editor did not restrict file names, extensions and paths of created and saved files, allowing privileged backend users to write arbitrary PHP files.
Git LFS is a Git extension for versioning large files. From 1.3.0 until 3.8.1, Git LFS does not correctly filter the limited set of options permitted in a repository's .lfsconfig file when option keys contain certain additional components. Crafted keys can mimic options that configure Git LFS to use a custom command to transfer objects, causing Git LFS to execute an attacker-selected command or binary while fetching objects. This issue is fixed in version 3.8.1.
Wing FTP Server before 8.2.8 contains a file mask bypass vulnerability allowing attackers to upload restricted files via an embedded NUL byte in Upload Link filenames. Attackers can plant a Lua session file with a chosen UID and send a matching UID cookie to execute operating system commands as the service account.
modified eCommerce Shopsoftware through 3.3.0 contains a local file inclusion vulnerability that allows administrators to include arbitrary server files by storing ../ sequences in the content manager file name. Unauthenticated requests to shop_content.php then pass the stored path to include(), executing embedded PHP in uploaded content files or images as the web server user.
HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, the CRAM decoder validates the 254-character query-name limit only after decoding the name into a 1024-byte stack array. An attacker-controlled CRAM record can provide an overlong query name and overflow the local stack buffer before the later validation runs; all CRAM format versions are affected. Opening such a file can crash the process, corrupt stack data, and may permit arbitrary code execution. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.
HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, the BCF reader can experience an integer overflow in a record-length check that verifies whether a record contains enough bytes for the expected number and size of stored items. A crafted BCF record can bypass this check, causing reads beyond the stored data and, in some cases, writes beyond the heap buffer when the reader sets the least significant bit of accessed bytes. Opening such a file can crash the process, corrupt data or heap structures, and may permit arbitrary code execution. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.
CVE-2026-99416 is a Linux kernel vulnerability in the overlay filesystem (overlayfs) related to handling the nlink extended attribute (xattr) of indexed non-directory files when nfs_export is enabled. This flaw can cause data loss when writing through a file handle to a lower-layer file and subsequent remounts, resulting in lookups returning errors and file handles remaining valid after file removal. The issue arises from incorrect handling of link counts and index entries, leading to data being lost and stale file handles persisting. The vulnerability has been fixed by modifying the function that reads the nlink xattr to correctly detect index entries and avoid skipping necessary reads.