Node.js HTTP client library undici versions 4.2.1 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1 contain a vulnerability where the client process crashes if a TLS 1.2 server renegotiates with a different CA-trusted certificate whose hostname does not match the requested host. This causes an uncaught assertion error that terminates the Node.js process, affecting both HTTP/1.1 and HTTP/2. The issue is fixed in versions 6.29.1, 7.30.1, and 8.12.2. Users should upgrade or restrict connections to TLS 1.3 to mitigate the risk.
Node.js HTTP client library undici versions 7.15.0 through 7.30.0 and 8.0.0 through 8.12.1 contain a vulnerability in the decompress interceptor. This interceptor forwards decompressed response data from zlib stream event callbacks without catching exceptions thrown asynchronously. As a result, if a downstream handler throws an exception asynchronously (e.g., the built-in dump interceptor when a response exceeds its maximum size), the exception is uncaught and terminates the Node.js process. A malicious or compromised HTTP server can exploit this by sending a small compressed response that decompresses to a size exceeding the limit, causing a client crash. The issue is fixed in versions 7.30.1 and 8.12.2 and later.
Node.js undici HTTP client versions 6.5.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1 contain a vulnerability in the EventSource client that allows a malicious Server-Sent Events peer to exhaust process memory. This occurs by sending many tiny completed data fields without blank event separators or a single unfinished line split across many chunks, causing unbounded parser state retention. The impact is denial of service via process termination due to memory exhaustion. The issue is fixed in versions 6.29.1, 7.30.1, and 8.12.2. No workaround exists other than upgrading.
Node.js HTTP client library undici versions 5.15.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1 contain a vulnerability in their WebSocket client. A malicious or compromised WebSocket server can cause the client to exhaust process memory by sending continuous small PING frames, which triggers automatic PONG responses that ignore backpressure signals. This leads to unbounded growth of the outbound write queue and heap, eventually causing the Node.js process to run out of memory and terminate. The issue affects availability only and requires no authentication. Fixed versions are 6.29.1, 7.30.1, and 8.12.2 and later. No workaround exists other than upgrading.
AdonisJS HTTP Server is a package for handling HTTP requests in the AdonisJS framework. Prior to 8.2.2 and 9.1.1, the regular expression returned by router.matchers.slug() contains adjacent greedy repetitions with overlapping character classes. When an application applies this matcher to an attacker-controlled route parameter, a long slug ending in a character rejected by the final assertion causes quadratic backtracking and excessive CPU use. Route matching occurs before route and group middleware, so authentication or rate-limiting middleware attached to the route may not prevent an unauthenticated request from blocking the Node.js event loop and stopping the worker from serving unrelated requests or health checks. This issue is fixed in versions 8.2.2 and 9.1.1.
CVE-2026-55240 is a critical vulnerability in the open source Tianji platform prior to version 1.31.29. It involves improper neutralization of special elements in a template engine, allowing a workspace administrator to inject server-side JavaScript code via templates. This code executes in the Node.js process when an unauthenticated user submits a survey response, potentially enabling command execution, secret disclosure, data modification, or service disruption. The issue is fixed in version 1.31.29.
An unauthenticated remote attacker can bypass authentication and gain full access to administrative API endpoints in Nutanix Prism Element by including a crafted internal management HTTP header. The vulnerability is caused by a misconfiguration in the application's authentication filters.
Consequently, the server responds with a Set-Cookie header containing a valid JSESSIONID. This session cookie decodes to a JSON Web Token (JWT) granting maximum cluster administrative privileges. Successful exploitation allows the attacker to execute root-level commands on all Controller VMs (CVMs) in the cluster, leading to complete cluster destruction and unauthorized access to VM memory and virtual disks.
Node.js HTTP client library undici versions 8.11.0 and 8.11.1 contain a vulnerability in the experimental WebSocket client enabled by default with HTTP/2. A failed WebSocket handshake over HTTP/2 leaves an HTTP/2 stream open without error handling, causing an unhandled error that crashes the Node.js process. This allows a remote unauthenticated server to cause a denial of service by crashing clients that open WebSocket connections over HTTP/2. The issue is fixed in version 8.11.2.
Nodemailer versions from 3.0.0 up to but not including 10.0.10 contain a denial of service vulnerability due to quadratic complexity in the SMTP client reply parser. This flaw allows a malicious SMTP server or an attacker in the network path to send specially crafted continuation lines without a completion line before authentication, causing the Node.js event loop to block and memory to be exhausted.
Nodemailer versions 3.0.0 before 10.0.13 contain a regular expression denial of service (ReDoS) vulnerability in the SMTPConnection._actionEHLO function. This vulnerability arises from overlapping whitespace sub-patterns in four AUTH mechanism detection regexes, causing quadratic backtracking. A malicious or man-in-the-middle SMTP server can exploit this by sending a crafted EHLO response with a long whitespace run and a non-matching token, which blocks the Node.js event loop for an extended period, potentially from tens of seconds to hours.
flytohub flyto-core versions 2.26.2 and 2.26.3 contain a command injection vulnerability in the HTTP MCP POST /mcp route. This flaw allows unauthenticated JSON-RPC calls to execute arbitrary shell commands via the sandbox.execute_shell module, potentially leading to full OS command execution with the privileges of the flyto-core server process. The issue is resolved in version 2.26.4.
A Server-Side Request Forgery (SSRF) vulnerability exists in redash versions from 10.0.0 up to but not including 26.9.0. The JSON data source query runner improperly combines a configured base URL with a user-supplied query URL, allowing an absolute URL to override the base URL. This enables users with execute_query permission to make server-side requests to arbitrary external origins. If HTTP Basic Authentication is configured, credentials may be forwarded to these external origins. Private IP blocking can be enforced via REDASH_ENFORCE_PRIVATE_IP_BLOCK. The issue is fixed in version 26.9.0.
A vulnerability in Angular.js versions prior to 20.3.31, 21.2.23, and 22.1.6 allows the @angular/platform-server DOM emulation parser to enter an infinite synchronous loop when processing attacker-controlled HTML with an incomplete DOCTYPE ending in whitespace. This causes high CPU consumption and event loop starvation in Node.js server-side rendering workers, potentially leading to denial of service. The issue is fixed in the specified versions.
CVE-2026-101896 is a high-severity vulnerability in the @angular/router URL parser affecting server-side rendering (SSR) in Node.js environments. Prior to fixed versions 20.3.32, 21.2.24, and 22.2.0, the router stores numeric matrix parameter names and numeric outlet names as properties on JavaScript objects. This can cause V8 to allocate large dense arrays, leading to excessive heap consumption. An unauthenticated attacker can exploit this by sending crafted requests with repeated numeric parameters, exhausting the Node.js heap and terminating the SSR worker. Pure client-side Angular applications are not affected. The issue is fixed in the specified versions.
CVE-2026-110385 is a high-severity remote code execution vulnerability in ONLYOFFICE Document Server versions before 10.0.0. It allows an authenticated attacker with a valid Inbox-compatible JWT to execute arbitrary OS commands as the ds service account. The vulnerability arises from improper processing of user-controlled converter XML in the Document Builder API, enabling path override and arbitrary file write outside the job directory. This can lead to overwriting the runtime.json configuration file and modifying executable paths and arguments, resulting in command execution during subsequent Document Builder jobs.
CVE-2026-84994 is a high-severity vulnerability in the Qwik JavaScript framework prior to versions 1.20.0 and 2.0.0-beta.37. It involves uncaught exceptions caused by improper handling of thenables during server-side JSON deserialization. An unauthenticated attacker can send specially crafted requests that cause the Node.js server to terminate due to unhandled promise rejections, resulting in denial of service. This can crash a single server or keep multiple replicas unavailable. The issue is fixed in the specified versions.
yt-dlp-web-ui versions up to 4.0.0 contain a NULL pointer dereference vulnerability in the Service.Formats JSON-RPC method. This flaw allows remote unauthenticated attackers to crash the server by sending a specially crafted request with a url value such as --version, which triggers invalid JSON output and an unrecovered panic that terminates the process.
yt-dlp-web-ui versions up to 4.0.0 have an argument injection vulnerability that allows unauthenticated remote attackers to inject command-line options by supplying specially crafted dash-prefixed URL parameters to the Service.Formats JSON-RPC method. This can cause the application to load attacker-controlled JSON files from the server filesystem, which are then reflected in responses. The vulnerability is fixed in version 4.0.1.
In Progress ShareFile Storage Zones Controller v5.12.6 and below, improper validation of outbound request destinations and parameters, unsafe JSONP response formatting, and insufficient validation on queue service can be chained by a remote unauthenticated attacker to issue server-side requests to unintended local handlers and perform unauthorized queue operations.