Electron versions prior to 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5 have a vulnerability where HID and USB permission checks made from iframes can be attributed to the wrong origin. This occurs because the permission check handler receives the top-level frame's origin instead of the requesting iframe's origin, potentially allowing embedded frames to gain access intended only for the top-level page. The issue affects apps using origin-based logic in setPermissionCheckHandler for HID or USB permissions and embedding cross-origin iframes with these permissions allowed. The vulnerability has a medium severity with a CVSS score of 5.4 and has been fixed in the specified versions.
CVE-2026-114125 is a code injection vulnerability in Storybook, a frontend UI component development tool. Versions from 8.0.0 up to but not including 8.6.19, 9.0.0 up to 9.1.21, 10.0.0 up to 10.6.2, and 11.0.0-alpha.0 up to 11.0.0-alpha.6 are affected. The flaw allows a malicious website to interact with the preview iframe of a running Storybook development server due to insufficient iframe embedding and message-origin restrictions. An attacker can cause unauthorized changes to story files if a developer visits and interacts with the malicious site, potentially leading to arbitrary code execution with the developer's privileges when the modified files are executed locally. Fixed versions include 8.6.19, 9.1.21, 10.6.2, and 11.0.0-alpha.6.
The npm package data-pipeline-testmetest version 2.0.1 contains malicious code that executes during installation without a declared install script. It uses a binding.gyp file to run an obfuscated loader that decrypts and executes a large payload. This payload steals credentials from GitHub, npm, PyPI, RubyGems, and cloud services, then commits them to a public GitHub repository created in the victim's account. It also republishes the victim's packages with the same malicious hook. If a GitHub token is found, it installs a destructive service that deletes the user's home directory once the token is revoked. Removal of this service before token revocation and credential rotation is necessary to prevent data loss.
The npm package event-emitter-testmetest contains malicious code in specific versions that use multi-layer obfuscation to execute attacker-controlled payloads. Versions 1.0.6 and 1.0.7 run an obfuscated loader that decrypts and executes code on load or during npm install via a binding.gyp hook. Versions 4.1.0 and 5.0.0 include a stealer payload executed similarly through binding.gyp. Other versions do not contain executable payloads.
The npm package 'peptide-modify' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, uncompromised machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package my-auto-follow-eltio@1.0.0 is a fork of the Baileys WhatsApp library that includes obfuscated code. Although the visible code does not show direct malicious actions such as remote code execution or credential theft, the package is flagged by a malware source as fully compromising any computer on which it is installed. It is recommended to consider any system with this package compromised, rotate all secrets from a clean system, and remove the package.
The @alannxd/baileys npm package is a malicious third-party fork of the legitimate @whiskeysockets/baileys WhatsApp library. Upon import, it performs an HTTPS GET request to a mutable URL controlled by the author, revealing the consumer's IP address. Although it does not execute remote code or exfiltrate credentials directly, the package poses a risk due to its namespace confusion potential and the import-time beacon to an author-controlled source. Security sources warn that any system with this package installed should be considered fully compromised, recommending immediate secret and key rotation and package removal.
The npm package tellyo-colours version 21.3.1 includes a runtime dependency on abbishal-poc-as-dependency with a wildcard version, allowing arbitrary code execution during installation. This dependency can fetch and run any version published by the dependency's controller, potentially executing malicious lifecycle scripts. The package is considered fully compromising any system where it is installed, requiring immediate secret and key rotation and removal of the package.
An incomplete fix in @angular/common's HttpClient for CVE-2025-66035 allows Cross-Site Request Forgery (XSRF) tokens to be leaked to attacker-controlled cross-origin domains due to discrepancies between a regular expression used for URL detection and the browser's WHATWG URL parser. This affects Angular versions prior to 21.0.3 and 20.3.34, where the XSRF token header may be attached to requests that the browser resolves as cross-origin. The vulnerability enables attackers to capture valid XSRF tokens if their server accepts the request and custom header via CORS, potentially enabling CSRF attacks. The issue is fixed in Angular 21.0.3, all 22.x releases, and 20.3.34 by replacing the regex with a proper origin comparison using the standard URL constructor.
markdown-it versions 14.1.0 through before 14.3.3 and 15.0.0 through before 15.0.3 contain a regression causing quadratic-time complexity when rendering a single multi-line link reference definition with default options. This results in severe performance degradation, blocking the Node.js event loop for many seconds on large inputs. The issue arises from inefficient string concatenation and parsing logic in the reference rule, leading to an algorithmic complexity denial of service (CWE-407).
markdown-it versions prior to 14.3.3 and from 15.0.0 up to but not including 15.0.3 have a vulnerability where enabling HTML parsing causes quadratic-time denial of service during inline HTML parsing. Specifically, repeated unterminated HTML constructs such as comments, processing instructions, declarations, and CDATA sections cause the parser to perform excessive repeated scans, blocking the Node.js event loop for seconds or tens of seconds. The default configuration disables HTML, but the commonmark preset enables it, making some applications vulnerable. A fix is available.
A vulnerability in @modelcontextprotocol/server versions 2.0.0 through 2.2.0 allows an MCP server accessed over HTTP to deliver one client's responses and notifications to another client when clients share a stateless transport or a single server instance. This occurs because messages are matched only by JSON-RPC id, which can collide. The issue is fixed in version 2.3.0 and later, but requires code changes to avoid sharing SDK clients or server instances across multiple clients.
A vulnerability in the MCP TypeScript SDK and server allows a single HTTP request within the default 4 MiB size limit to exhaust server memory during validation by sending excessive array elements or object keys. This causes the server process to abort with a 'JavaScript heap out of memory' error. No authentication is required unless the server enforces it before the SDK processes requests. The issue affects versions 1.3.0 through 1.31.0 of @modelcontextprotocol/sdk and 2.0.0 through 2.2.0 of @modelcontextprotocol/server. Fixed versions are 1.32.0+ for the SDK and 2.3.0+ for the server, which introduce a new option to limit input elements and recommend lowering request size limits.
The MCP TypeScript SDK versions prior to specified patched releases accept bearer tokens issued for other services due to lack of audience (aud) validation in server-side authentication. This allows tokens valid for one service to be accepted by another MCP server using the SDK, if the authorization server issues tokens for multiple services. The issue affects multiple MCP SDK and server packages in versions before 1.32.0, 2.3.0, 2.0.2, and 2.3.1 respectively. A fix is available that adds an optional expectedResource setting to enforce audience validation, which must be enabled explicitly. Without enabling this setting or applying a custom audience check, the vulnerability remains exploitable.
The npm package '@securihackbot/depconf-stage-1792484738' contains malicious code in its postinstall hook that automatically executes upon installation. This code collects system information including hostname, local username, platform/architecture, Node.js version, package name, and a nonce, then encodes and sends this data via an unencrypted HTTP GET request to a hardcoded IP address. The package is designed to be used in dependency confusion attacks by being republished under victim-internal scopes, causing internal package resolution to fetch this malicious package from the public registry and leak sensitive environment information to the attacker.
The npm package rs-lookout-sandbox-poc version 1.0.1 contains malicious code that, upon being loaded, automatically collects the local system username and sends it to an external third-party URL. Additionally, it performs reconnaissance on the AWS Instance Metadata Service by attempting to retrieve an IMDSv2 token and enumerating IAM role credentials associated with the host. These actions occur without any explicit invocation by the user.
The npm package 'memories-core-web' version 99.0.0 contains a malicious preinstall script that automatically executes during installation. This script sends the installer's hostname and username to a third-party webhook.site URL, which is unrelated to the package publisher. This behavior results in unauthorized data exfiltration during the npm install process.
The npm package nwfp-build-config contains malicious code that exfiltrates user identity data via a covert DNS tunnel. Upon requiring the package, it encrypts the host's hostname and username using a hardcoded AES-256-CBC key, encodes the data, and sends it through DNS queries to an external domain unrelated to the package's stated purpose. This behavior indicates identity theft and unauthorized data leakage. Systems with this package installed should be considered fully compromised, and all secrets and keys should be rotated. Removal of the package alone may not fully remediate the compromise.
ApostropheCMS versions prior to 4.34.0 and import-export module versions prior to 3.7.1 contain a missing authorization vulnerability. An editor with import permissions but lacking stronger publication roles can improperly create, replace, or remove published content variants without the usual publish permission and lifecycle checks. This flaw allows unauthorized modification of published content through import write helpers. The issue is resolved in ApostropheCMS 4.34.0 and import-export 3.7.1.
ApostropheCMS versions prior to 4.34.0 and sanitize-html versions 2.18.0 before 2.18.1 contain an uncontrolled recursion vulnerability. This occurs when an <iframe> tag is disallowed and disallowedTagsMode is set to 'discard', causing recursive calls to sanitizeHtml without a termination condition. The flaw leads to a denial of service by exhausting resources. The issue is fixed in versions 4.34.0 of ApostropheCMS and 2.18.1 of sanitize-html.