Node Version Manager (nvm) versions 0.40.0 through 0.40.8 have a vulnerability where the authorization header set in NVM_AUTH_HEADER is passed as a visible command-line argument to curl or wget during downloads. This exposure allows other local users on the same machine to potentially read sensitive tokens via process listings. The issue is fixed in version 0.41.0, which changes the method of passing the header to avoid command-line exposure.
Node Version Manager (nvm) versions 0.39.6 through 0.40.8 contain an OS command injection vulnerability in the handling of remote LTS aliases. The vulnerability arises because the version column from the mirror's index.tab file is stored without validation and later evaluated in shell arithmetic, allowing command substitution execution under bash and zsh. Exploitation requires use of a hostile mirror or man-in-the-middle attack and running affected nvm commands. The issue is fixed in version 0.41.0 by restricting arithmetic evaluation to numeric offsets and dropping invalid version strings.
CVE-2026-102894 is a critical authentication bypass vulnerability in GPUStack versions from 0.7.1 up to but not including 2.2.2. The vulnerability occurs because the /auth/saml/callback endpoint fails to verify SAML response signatures and related security conditions, allowing attackers to impersonate existing users or provision new accounts without proper authentication. This flaw is fixed in version 2.2.2.
CVE-2026-102895 is a critical improper authentication vulnerability in GPUStack versions prior to 2.2.0. The flaw allowed remote attackers to bypass authentication by exploiting how loopback requests were treated as administrator requests when force_auth_localhost was false. This led to unauthenticated administrative access, enabling changes to users and models, creation of persistent admin API keys, disclosure of secrets, and remote code execution. The issue was fixed in version 2.2.0.
CVE-2026-122015 is a medium severity vulnerability in NPC-Worldwide npcpy versions 2.1.0 through 2.1.19. It involves improper input validation in the get_mlx_response function of the MLX Provider component, specifically in the npcpy/gen/response.py file. The vulnerability can be exploited remotely by manipulating the 'model' argument. Public exploit code is available, but there are no known exploits in the wild. No patch or remediation information is provided.
CVE-2026-97693 is a critical command injection vulnerability in the Yuxi platform versions from 0.6.0.beta1 up to but not including 0.7.1. It allows a low-privileged authenticated user with command execution in their own Docker sandbox to access and manipulate other tenants' sandboxes and data without needing administrator credentials. The vulnerability arises from insufficient isolation between Docker sandboxes and trusted services, enabling cross-tenant API access, file and secret exposure, sandbox management, and potential command execution in shared internal services if default credentials remain unchanged. The issue is fixed in version 0.7.1, but deployments must also rotate persisted credentials for PostgreSQL, Neo4j, and MinIO if they were set to default values, as upgrading alone does not rotate these credentials.
Jan versions from 0.8.5 up to but not including 0.8.8 have a vulnerability that allows attackers to bypass workspace protections and write files outside the intended workspace by exploiting dangling symbolic links. This can be triggered by supplying a malicious repository and using prompt injection to cause file write or edit tools to follow symlinks, potentially creating sensitive files such as ~/.ssh/authorized_keys on the host system.
jsondiffpatch versions before 0.7.7 contain a cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious markup by providing an unescaped array-move destination index in a delta object. Exploitation requires control over the delta passed to the formatters.html.format() or formatters.annotated.format() functions, enabling script execution in the application's origin context. The vulnerability is fixed in version 0.7.7.
CVE-2026-122233 is an information disclosure vulnerability in FrankenPHP versions before 1.13.4. The flaw occurs in worker mode where the last HTTP stream response headers are not cleared between requests because the reset only happens during RSHUTDOWN, which worker requests skip. This allows subsequent requests on the same worker thread to access headers from previous requests, potentially exposing sensitive headers such as Set-Cookie or tokens from backend APIs.
CVE-2026-16725 is a path traversal vulnerability in IBM Watson Speech Services Cartridge versions 4.0.0 through 5.4.0. This flaw allows a remote authenticated attacker to read arbitrary files on the local filesystem. The vulnerability does not require user interaction and impacts confidentiality but not integrity or availability.
CVE-2026-19319 is an out-of-bounds read vulnerability in IBM Watson Speech Services Cartridge versions 4.0.0 through 5.4.0. This flaw could allow a remote attacker to obtain sensitive information without requiring authentication or user interaction. The vulnerability has a medium severity rating with a CVSS score of 5.3.
CVE-2026-82418 is a critical use-after-free vulnerability in IBM Watson Speech Services Cartridge versions 4.0.0 through 5.4.0. This flaw could allow a remote attacker to execute arbitrary code without any user interaction or privileges.
CVE-2026-17493 is an out-of-bounds read vulnerability in IBM Watson Speech Services Cartridge versions 4.0.0 through 5.4.0. This flaw could be exploited remotely to cause a denial of service condition. The vulnerability does not impact confidentiality or integrity but results in service disruption.
A vulnerability has been found in NPC-Worldwide npcpy up to 2.1.27. This affects the function load_sft_model of the file npcpy/ft/sft.py. The manipulation of the argument base_model_name_or_path leads to code injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
IBM Db2 Genius Hub versions 1.1.2 through 1.1.5 contain a vulnerability where error messages expose sensitive internal implementation details. This information disclosure could be exploited by a remote authenticated attacker to gain sensitive information. The vulnerability is classified under CWE-209 and has a medium severity with a CVSS score of 4.3.
IBM Db2 Genius Hub versions 1.1.2 through 1.1.5 have a vulnerability where a missing Content Security Policy (CSP) header could allow a remote authenticated attacker to bypass certain security restrictions. The issue is classified under CWE-693, indicating a protection mechanism failure. The vulnerability has a low severity score of 3.5 and does not impact confidentiality, integrity, or availability significantly.
IBM Db2 Genius Hub versions 1.1.2 through 1.1.5 contain a vulnerability where improper restriction of rendered UI layers or frames allows a remote authenticated attacker to bypass security restrictions. This issue could lead to limited confidentiality and integrity impacts but does not affect availability. The vulnerability has a medium severity rating with a CVSS score of 4.6.
IBM Db2 Genius Hub versions 1.1.2 through 1.1.5 have a security vulnerability where the absence of the X-Content-Type-Options header allows MIME type sniffing. This can enable a remote authenticated attacker to bypass security restrictions. The vulnerability is classified under CWE-693 (Protection Mechanism Failure) and has a medium severity rating with a CVSS score of 5.4.
IBM Db2 Genius Hub versions 1.1.2 through 1.1.5 contain a vulnerability that allows remote authenticated attackers to perform HTTP response splitting due to improper neutralization of HTTP headers. This vulnerability is identified as CWE-113 and has a medium severity rating with a CVSS score of 4.3.
IBM Db2 Genius Hub versions 1.1.2 through 1.1.5 contain a vulnerability that allows a local attacker to cause a denial of service by triggering uncontrolled resource consumption. The vulnerability is identified as CWE-400 and results in availability impact without affecting confidentiality or integrity.