The @tsparticles/mcp-server package contains a vulnerability in its HTTP server mode where the POST /mcp endpoint accumulates incoming request body chunks into memory without size limits. This allows an unauthenticated remote attacker to send an arbitrarily large request body, causing the Node.js process to exhaust memory and crash, resulting in a denial of service. The official Docker image runs this HTTP mode by default, making the vulnerability exploitable in typical container deployments. A fix is available in version 4.3.1 that adds a request body size limit.
CVE-2026-123811 is a vulnerability in dynatrace-mcp versions prior to 2.0.0 where the server started with the --http option accepts JSON-RPC requests without authentication or session validation. This allows network-reachable attackers to invoke certain functions such as execute_dql to read sensitive data like logs and security events, or create_dynatrace_notebook to create tenant-visible notebooks. The issue is fixed in version 2.0.0.
CVE-2026-123807 is a critical path traversal vulnerability in Signal K Server and its resources provider plugin. It affects versions from 2.0.0 up to but not including 2.34.0 for signalk-server, and 1.0.0 up to but not including 1.5.3 for @signalk/resources-provider. The vulnerability allows an attacker to read, write, or delete arbitrary JSON files on the server by exploiting insufficient path containment in the REST API resource handling. This can lead to exposure of sensitive files such as security.json, which contains JWT signing secrets and password hashes. With this information, an attacker can forge administrator tokens and gain administrative access to execute commands with server privileges. The issue is fixed in versions 2.34.0 and 1.5.3 respectively.
In November 2026, threat actors compromised Ethersphere's release pipeline, publishing malicious versions of the @ethersphere/bee-js npm package and Swarm Desktop releases. These trojanized artifacts contained loaders that fetched JavaScript with full Node.js privileges from a malicious server and used an Ethereum smart contract for command and control. The malware exfiltrated sensitive data such as Bee node passwords and wallet keys, and deployed backdoors and remote access tools targeting developers working with Ethereum tooling. The compromised releases were signed and published through legitimate workflows, making detection more difficult.
Allocation of Resources Without Limits or Throttling vulnerability in Apache Axis2/Java. The JSON message builders, including the Gson, Moshi and HTTP/2 variants, buffered the entire request body with no size limit, so an unauthenticated caller could exhaust server memory with a large JSON request. Version 2.0.2 bounds JSON request bodies with the configurable jsonMaxRequestSize parameter. This issue affects Apache Axis2/Java: through 2.0.1. Users are recommended to upgrade to version 2.0.2, which fixes the issue.
The Grav Lightbox Gallery plugin versions 1.1.0 up to but not including 1.3.2 on Grav 2.x allows page editors to invoke any medium method named in image, thumb, or thumb_options shortcode values without proper core media action checks. This flaw enables an attacker with page editing privileges to chain methods such as addMetaFile with value, toYaml, or toJson to read server-readable YAML files, potentially exposing sensitive information like account password hashes, two-factor authentication secrets, and API keys in publicly accessible pages.
CVE-2026-123569 is a high-severity vulnerability in the sveltejs devalue package before version 5.6.3. It allows an attacker to cause excessive CPU and memory consumption by serializing sparse arrays on the server, potentially leading to a denial of service. This issue arises because the package does not limit or throttle resource allocation during serialization of such arrays. The vulnerability is fixed in version 5.6.3.
A critical Server-Side Request Forgery (SSRF) vulnerability exists in open-wanderer wanderer versions prior to 0.20.0. When the configuration PUBLIC_PRIVATE_INSTANCE is not set to true, an unauthenticated attacker can send a POST request to /api/v1/trail/download with a crafted JSON url field. This input is directly used in a fetch call, allowing the attacker to make requests to internal network services, cloud metadata endpoints, and other network destinations. This can lead to exposure of sensitive internal data and potential denial of service. The vulnerability is fixed in version 0.20.0.
CVE-2026-102650 is a high-severity vulnerability in Nuxt Content versions from 3.0.0 up to but not including 3.15.2. The unauthenticated POST endpoint /__nuxt_content/:collection/query accepts attacker-controlled SQL input that allows expensive SQLite expressions, leading to uncontrolled resource consumption. This can cause substantial CPU and memory usage, blocking the Node.js event loop and concurrent request handling. Fully static prerendered deployments that do not expose the server endpoint are not affected. The issue is fixed in version 3.15.2.
CVE-2026-123846 is a server-side request forgery (SSRF) vulnerability in JetBrains IntelliJ IDEA versions before 2026.3. The flaw allows blind SSRF via remote references in JSON Schema validation. It has a CVSS 3.1 base score of 4.3, indicating medium severity. The vulnerability is fixed in version 2026.3.
CVE-2026-123487 is a high-severity vulnerability in parse-community's parse-server affecting versions before 8.6.115 and 9.0.0 before 9.10.7-alpha.1. The issue arises from inefficient regular expression complexity used to validate user email addresses, which grows quadratically with input length and lacks length limits. This allows an unauthenticated attacker or a logged-in user to submit a crafted long email address that blocks the Node.js event loop, causing a denial of service (DoS) for all clients.
CVE-2026-120222 is a vulnerability in the undici HTTP client for Node.js affecting versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3. When the cache interceptor is used with a downstream response handler that throws during processing, an asynchronous throw can escape as an uncaught exception or unhandled promise rejection, causing the Node.js process to terminate. This can be triggered by a malicious or compromised HTTP server serving a cacheable response that causes the throw on replay, impacting availability. The issue is fixed in versions 7.30.2 and 8.12.4. Users are advised to upgrade to these fixed versions or later or avoid composing the cache interceptor with such response handlers until upgrading.
CVE-2026-123087 is a high-severity SQL injection vulnerability in Atmira's SIREC product. The vulnerability arises because the server retrieves a field value from a user-supplied JSON object and concatenates it directly into an SQL query without proper sanitization. This flaw allows attackers to alter the original SQL query, potentially causing the database to return unauthorized or unexpected information. The vulnerability affects version 0 of SIREC and was fixed on 16 October 2026.
A SQL Injection vulnerability (CWE-89) exists in Kubeflow Pipelines prior to version 2.17.0. The API server improperly trusts structural SQL identifier fields decoded from the base64-encoded JSON page_token parameter when constructing list queries. This allows an attacker with permission to invoke pipelines or run list API calls to inject SQL via KeyFieldName or SortByFieldName parameters, potentially reading data accessible to the API server database account across namespaces. No database modification has been established. The issue is fixed in version 2.17.0.
Versions 1.11.2 through 1.11.6.1 of the noname Electron desktop build contain an unauthenticated local file server with a wildcard CORS policy. This vulnerability allows malicious websites to send cross-origin requests to the local server on port 8089, enabling them to read, overwrite, or delete installation files. Specifically, attackers can overwrite renderer scripts, resulting in execution of arbitrary JavaScript with Node.js privileges as the local user.
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 2.0.0 until 2.3.0 in @modelcontextprotocol/server, applications that shared one stateless HTTP transport or one McpServer or Server instance among multiple clients could deliver responses and notifications to the wrong client. The affected surface is an MCP server reached over HTTP by multiple clients. The trigger is reuse of one stateless transport or server instance. Messages were associated with a connection using only the JSON-RPC request identifier. SDK clients start request identifiers at zero, so collisions occur in normal operation. Cross-client delivery exposes one client's responses and notifications to another client. The issue requires an HTTP endpoint reachable by more than one client and an application that constructs the server or transport once at startup instead of once per request or session. stdio servers and factory-created per-call servers are not affected. Upgrading causes reused instances to fail and therefore requires an application code change. This issue is fixed in @modelcontextprotocol/server 2.3.0.