An information exposure vulnerability in the job scheduling component of SANnav allows sensitive credentials to be written to application logs in plain text. When scheduled support save jobs or related operational tasks are executed, sensitive parameters including external server passwords and archive protection keys are logged without proper masking. A local or authenticated user with access to application logs or support bundles can view these cleartext credentials, potentially leading to unauthorized access to remote backup targets or protected archives.
Dell Trusted Device Client versions prior to 8.1.359.0 have an incorrect permission assignment vulnerability. This flaw allows a low privileged local attacker to tamper with information. The vulnerability does not require user interaction and affects confidentiality and integrity but not availability. It has a high severity score of 7.1.
CVE-2026-89325 is a high-severity vulnerability in Rapid7 Insight Agent on Windows involving an uncontrolled search path element. A local, low-privileged user can execute arbitrary code as SYSTEM by placing a malicious executable named 'code' in a writable directory that appears earlier in the machine PATH than the legitimate Visual Studio Code. This affects all Insight Agent versions running assessment content at or below version 0.0.261.0. The issue was fixed in assessment content version 0.0.269.0, which was automatically deployed, requiring no customer action.
Dell Rugged Control Center (RCC), versions prior to 5.2.206, contain an Improper Authorization vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of Privileges.
Dell Rugged Control Center (RCC), versions prior to 5.2.206, contain an Improper Authorization vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of Privileges.
TREK is a collaborative travel planner. Prior to 3.4.0, the checkSsrf logic in server/src/utils/ssrfGuard.ts does not recognize NAT64, 6to4, or Teredo IPv6 transition addresses that encode an IPv4 destination. An authenticated user who controls a DNS record can supply a URL whose AAAA result is a transition address embedding a private, loopback, or link-local IPv4 target, and isAlwaysBlocked and isPrivateNetwork classify the address as allowed. In a deployment that routes the applicable transition format, user-facing imports, webhooks, integrations, or plugin egress can reach internal services or cloud metadata and expose returned information. This issue is fixed in version 3.4.0.
TREK is a collaborative travel planner. Prior to 3.3.0, TREK allows an authenticated user to store an attacker-controlled llm_base_url through the settings API when the LLM_PARSING feature is enabled. Write permission to the target trip instance is required to trigger the vulnerable AI-assisted import path. The value is consumed by the clients in server/src/nest/llm-parse/clients/openai-compatible.client.ts, server/src/nest/llm-parse/clients/anthropic.client.ts, and server/src/nest/llm-parse/router/ollama-format.client.ts without applying the server-side request forgery guard. Triggering AI-assisted trip parsing causes the server to request the supplied destination, and upstream error response text can be returned in parsing warnings. This permits internal service discovery and access to link-local cloud metadata, with possible disclosure of infrastructure credentials and subsequent modification of protected cloud resources. This issue is fixed in version 3.3.0.
http4s-scala-xml provides `EntityDecoder[F, scala.xml.Elem]` instances that parse XML message bodies. Prior to versions 0.24.1 and 1.0.0-M39, these decoders used a `javax.xml.parsers.SAXParserFactory` obtained from `SAXParserFactory.newInstance` without any security configuration. With the JDK's default settings, the parser resolves DOCTYPE declarations, external general and parameter entities, and external DTDs.An application that uses these decoders to parse untrusted XML is vulnerable to XML External Entity (XXE) attacks. An attacker can craft a request that discloses local files readable by the service process, performs server-side request forgery (SSRF) against internal network resources, and/or causes denial of service through entity expansion. Versions 0.24.1 and 1.0.0-M39 fix the issue.
A vulnerability in the Linux kernel's wifi libipw component was resolved that involved improper boundary checks when reading the WEP key index from network packet data. The function libipw_rx() previously checked for skb->len >= hdrlen + 3 before reading skb->data[hdrlen + 3], which did not sufficiently ensure the byte was within bounds. The fix requires hdrlen + 4 bytes before accessing that byte, preventing a potential out-of-bounds read. This is a local source-boundary check and does not affect key index semantics.
A buffer overflow vulnerability in the Linux kernel's ACPICA component was resolved by enhancing buffer validation in the acpi_ut_walk_aml_resources() function. This vulnerability could allow local attackers to cause denial of service or potentially escalate privileges. The issue affects specific Linux kernel versions and has a CVSS score of 7.7, indicating a medium severity level.
`@bsv/wallet-toolbox` provides BRC-100 wallet signing and storage components, while `@bsv/wallet-toolbox-client` and `@bsv/wallet-toolbox-mobile` provide client-focused distributions for standard and mobile applications using wallet storage services. A vulnerability in these packages causes transactions created through a remote `StorageClient` to trust output locking scripts returned by the storage provider without verifying that they match the outputs requested by the caller. A malicious or compromised storage provider can substitute a recipient script or inject an additional output, causing the wallet to sign and broadcast a transaction that redirects funds while the application and user interface continue to display the intended recipient. Source and npm publication history indicate that stable versions `@bsv/wallet-toolbox` and `@bsv/wallet-toolbox-client` from 1.1.47 through 2.3.3, and `@bsv/wallet-toolbox-mobile` from its initial 1.3.21 release through 2.3.3, are affected. All three packages are patched in version 2.4.0. Applications unable to upgrade should avoid remote `StorageClient` providers, use local storage, or independently verify every transaction output’s locking script and value against the original request before signing
A vulnerability in the Linux kernel arm64 memory management subsystem was fixed involving the lockless page-table walk in the show_pte() function. The issue arises because show_pte() walks page tables without locks and with interrupts enabled, allowing a concurrent teardown to free a table page during the walk. This can cause dereferencing of freed memory or use of invalid pointers derived from cleared parent entries. The fix involves disabling local interrupts around the walk to prevent RCU-deferred table frees and blocking certain inter-processor interrupts until the walk completes, preventing invalid memory access during page-table walks.
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.5.0 until 2.5.1, the /homepage/proxy endpoint accepts an authenticated user's url query parameter and passes it to http.get or https.get without destination restrictions. In src/backend/database/routes/homepage-proxy-routes.ts, new URL performs only syntactic validation, allowing requests to loopback, RFC1918, link-local, and cloud metadata destinations. The endpoint returns the complete fetched JSON response, so a low-privilege or self-registered account can exfiltrate internal service data and cloud credentials. This issue is fixed in version 2.5.1.
CVE-2026-95521 is a command injection vulnerability in the rpm tool on Red Hat Enterprise Linux 10. It occurs when installing or rebuilding a source RPM with source or spec file basenames containing a %() macro, causing rpm to execute attacker-controlled shell commands via popen(). This allows arbitrary command execution as the invoking user, typically non-root, when processing untrusted source RPMs. Exploitation requires local user interaction to install or rebuild the malicious source RPM. The vulnerability is not exposed as a network service.
An input validation vulnerability exists in the PaperCut Hive embedded application for Ricoh devices. The application fails to properly sanitize input received during the NFC card reading process before passing it to the application's web view interface. A local attacker with physical access to the device and a specially crafted NFC card or emulator could exploit this flaw to execute arbitrary code within the context of the application's user interface. This could result in unauthorized actions or information disclosure.
Multiple security vulnerabilities have been identified in the Red Hat build of Keycloak, an open-source identity and access management solution. These issues include account takeover, path traversal allowing local file read, denial of service, session fixation, cross-site scripting, privilege escalation, and other authentication and authorization flaws. A security update is available in Keycloak version 26.6.8 that addresses these vulnerabilities.
IBM Concert 1.0.0 through 3.0.0 invokes operating system commands without fully qualifying executable paths or adequately restricting search path resolution. As a result, an attacker with local system access can manipulate the search path environment to execute untrusted or malicious code.
A vulnerability has been found in sfturing hosp_order up to 627f426331da8086ce8fff2017d65b1ddef384f8. This vulnerability affects unknown code of the file ssm_pro/src/main/java/cn/sfturing/service/impl/CommonUserServiceImpl.java. Such manipulation leads to cleartext storage of sensitive information. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.