A vulnerability in iperf3 server versions 3.0 and 4.0 allows remote denial of service due to the server accepting unbounded peer-controlled JSON parameters. This flaw can lead to resource exhaustion and service disruption.
NextAuth.js provides authentication for Next.js. From next-auth 5.0.0-beta.0 until 5.0.0-beta.32, applications that gate access by checking only for the existence of the auth object returned by the auth() wrapper can fail open when Auth.js has a server configuration error. In middleware, Route Handlers, React Server Components, and other auth() entry points, a non-OK session response is parsed into a truthy error object instead of null, so checks such as !!auth and if (req.auth) evaluate to true for unauthenticated requests. A provider missing both the issuer and authorization endpoint triggers InvalidEndpoints, and an unset AUTH_SECRET or another server configuration error can produce the same behavior. There is no impact while configuration is valid, but after a deployment becomes misconfigured, routes protected only by session existence silently grant access to every visitor. This issue is fixed in next-auth 5.0.0-beta.32.
CVE-2026-72851 is a critical unauthenticated SQL injection vulnerability in Budibase server versions before 3.40.0. It occurs in webhook-triggered automations that use EXECUTE_QUERY steps, allowing attackers to send malicious JSON payloads to the webhook endpoint. Exploitation enables execution of SQL commands with builder-configured database credentials, potentially leading to data exfiltration, modification, and persistence in connected datasources such as Snowflake. A patch is available to remediate this issue.
FreePBX is an open source IP PBX. Prior to 17.0.9, the UCP Node server on ports 8001 and 8003 uses io.use(checkAuth) in node/lib/server.js, but Socket.IO version 4 applies that middleware only to the default namespace. An unauthenticated client can connect to custom namespaces that do not consistently invoke checkAuth in node/lib/auth.js and send crafted event values containing carriage-return or newline characters through the Asterisk Manager Interface action path patched by node/lib/asterisk-manager-patch.js, allowing arbitrary commands to execute as the asterisk service user. This issue is fixed in version 17.0.9.
Style Dictionary versions from 5.0.0 up to but not including 5.4.4 contain a prototype pollution vulnerability in the convertTokenData utility function. This vulnerability allows a malicious user to inject tokens with keys like '{__proto__.foo}', which pollutes the global Object.prototype, potentially leading to high impact in NodeJS server applications. The vulnerability is patched in version 5.4.4. Workarounds include sanitizing token data to prevent keys containing '__proto__' and disabling the expand feature.
A memory leak vulnerability exists in honojs node-server versions prior to 2.0.10. When a WebSocket upgrade request with a missing or malformed Sec-WebSocket-Key header is sent to an upgradeWebSocket route, the IncomingMessage object is retained indefinitely due to a missing cleanup path. This allows an unauthenticated attacker to cause unbounded memory growth and potentially make the service unavailable. The issue is fixed in version 2.0.10.
The MCP Python SDK's deprecated WebSocket server transport does not validate Host or Origin headers during the WebSocket handshake, allowing any web page to connect and issue JSON-RPC requests if the server is exposed without additional protections. This affects applications that explicitly use the deprecated websocket_server transport, which is not part of the MCP specification and must be manually integrated. The vulnerability can lead to unauthorized enumeration and invocation of server tools and resource access depending on the server's exposure. The issue is fixed in version 1.28.1 by adding optional Host and Origin validation, but upgrading alone does not enable validation unless configured. The recommended mitigation is to migrate away from the deprecated transport to Streamable HTTP, which enforces these protections automatically. The WebSocket transport is removed entirely in version 2.
Repomix MCP server's attach_packed_output tool can bypass secret scanning when reading local .json, .txt, .md, or .xml files. This allows reading arbitrary local files without the secret check enforced by the file_system_read_file tool. The issue affects repomix versions from 0.2.1 up to but not including 1.14.1 and is fixed in version 1.14.1.
A memory leak vulnerability exists in the UltraJSON (ujson) library versions 5.4.0 through 5.11.0 when parsing large integers outside the range [-2^63, 2^64 - 1]. This flaw can be triggered by any service using ujson to parse untrusted JSON inputs, potentially leading to denial of service (DoS). The leak involves accumulating copies of the string representation of large integers plus a null byte, regardless of whether parsing succeeds or fails. The issue is fixed in ujson version 5.12.0. No workarounds other than upgrading are available.
CVE-2026-32875 is a vulnerability in the UltraJSON (ujson) library used by python-lsp-server where integer overflow or underflow in handling the 'indent' parameter during JSON serialization can cause a segmentation fault (crash) or an infinite loop. This occurs when the product of the indent value and the nested depth exceeds the 32-bit integer limit or when a large negative indent is used. The issue can lead to denial of service. The vulnerability affects python-lsp-server versions >=1.6.0 and <1.14.0_1. A patch is available in ujson 5.12.0 that fixes the overflow and caps the indent value.
Hub is a Node.js WebSocket server and client with added features. Prior to 0.2.16, every incoming unauthenticated WebSocket connection triggers loadDefaultConnectionEventListeners to call requestClientId, which calls rpc.send for the get-client-id action and pushes a request into RPC.requests. The RPC.waitForReply function starts a setInterval polling loop every 10 milliseconds that is cleared only after a matching reply; if the client remains silent and closes, the timer and pending request stay allocated because the socket close path does not cancel them. Repeated connections therefore cause unbounded timers and heap entries, exhausting CPU and memory and making the server unavailable. This issue is fixed in version 0.2.16.
OpenClaw CLI's Feishu webhook component reads and parses JSON request bodies before validating the request signature in versions up to 2026.3.24. This behavior allows unauthenticated callers to force the server to perform full JSON parsing on potentially malicious or large payloads before the request is rejected. The issue was fixed in version 2026.3.25 by changing the code to validate the signature on the raw request body before parsing JSON.
A vulnerability in n8n-mcp versions 2.14.1 through 2.47.10 allows sensitive request data to be logged on unauthorized POST /mcp HTTP requests. This includes bearer tokens, per-tenant API keys, and JSON-RPC payloads. Although unauthorized requests are rejected, sensitive information is still recorded in server logs, potentially exposing it if logs are accessible outside the trusted boundary. The issue affects deployments using HTTP transport mode and is fixed in version 2.47.11.
JupyterLab versions 3.3.0 up to but not including 4.6.2 contain a cross-site scripting (XSS) vulnerability via crafted settings files named overrides.json. This file can be imported by users or automatically loaded from configuration directories. The vulnerability allows embedded code in the settings file to execute with the user's privileges, potentially reading or modifying notebooks and running code on the notebook server and connected kernels. The issue arises because certain notebook display settings were not properly validated before application. Patches are available in versions 4.6.2 and later.
PyJWKClient in PyJWT versions before 2026.7.1 does not restrict URL schemes when fetching JSON Web Key Sets (JWKS), allowing attacker-controlled URLs with schemes like file://, ftp://, or data:. This can lead to server-side request forgery (SSRF) to local files or other resources. Additionally, if an attacker can write to a location referenced by a file:// URL, they can forge JWT tokens that the application will accept as valid. The vulnerability is fixed in version 2026.7.1 by adding an allowed schemes whitelist.
CVE-2024-24762 is a Regular Expression Denial of Service (ReDoS) vulnerability in the python-multipart library used by dstack and frameworks like FastAPI when parsing HTTP Content-Type headers in form data. An attacker can craft a malicious Content-Type header that causes the regex parser to consume excessive CPU resources, stalling the server's main event loop and causing denial of service. This vulnerability affects applications that parse form data with python-multipart but not JSON payloads. The issue is fixed in python-multipart version 0.14.0_2.
@jshookmcp/jshook is an MCP server that gives AI agents tools for JavaScript analysis and security research. In version 0.3.1, he network domain has a central SSRF authorization policy that blocks private, loopback, link-local, and reserved targets unless an explicit authorization object allows private network access. The policy is enforced by raw HTTP/TCP/TLS RTT tools, but the ICMP probe and traceroute tools resolve the target and invoke the native ICMP/traceroute sink directly. An MCP client with access to an active network domain can therefore ask the jshookmcp server to probe internal addresses even when local SSRF access is disabled for the other raw network tools. This exposes an internal reachability and route mapping primitive from the server network position. Version 0.3.2 fixes the issue.
The npm package datetime-fmt-xutil version 1.0.0 contains malicious code in its postinstall.js script. This script opens a TCP connection to a hardcoded IP address and pipes a shell to the remote endpoint, granting interactive shell access to an attacker. The malicious behavior executes unconditionally during npm install and uses fallback methods with bash and python3 to establish the reverse shell. Failures are reported via HTTP GET requests to the attacker's server. The package's legitimate date-formatting functionality is a cover for this reverse-shell payload.