A vulnerability in Thunderbird on Windows allows bypassing the check that prevents mailbox: URLs from accessing files on remote Windows network shares by using extended-length UNC paths. This can cause Thunderbird to connect to an attacker-controlled SMB server, leaking the user's Windows account name and NTLM authentication data. The leaked NTLM data could be used for offline password cracking or relay attacks. The issue affects only Thunderbird on Windows and was fixed in Thunderbird versions 153.6 and 159.
undici is vulnerable to a denial of service condition triggered by a TLS 1.2 server-initiated renegotiation presenting a different, valid but hostname-mismatched certificate. This causes an uncaught assertion error that crashes the Node.js client process, affecting both HTTP/1.1 and HTTP/2. Only TLS 1.2 is impacted, as TLS 1.3 does not support renegotiation. The issue is fixed in undici versions 6.29.1, 7.30.1, and 8.12.2. Mitigation includes upgrading to these versions or restricting connections to TLS 1.3 to prevent renegotiation.
undici's WebSocket client, including Node.js's bundled globalThis.WebSocket, is vulnerable to a denial of service condition caused by unbounded automatic PONG buffering. A malicious WebSocket server can send continuous PING frames causing the client to queue PONG responses without respecting backpressure, leading to memory exhaustion and process termination. This affects undici versions from 5.15.0 up to but not including 6.29.1, 7.0.0 up to 7.30.1, and 8.0.0 up to 8.12.2. Upgrading to versions 6.29.1, 7.30.1, or 8.12.2 mitigates the issue by properly handling backpressure.
A vulnerability in undici's decompress interceptor allows a denial of service via an unhandled exception. When the decompress interceptor forwards decompressed data to a downstream handler that throws an exception asynchronously (such as the dump interceptor with a maxSize limit), the exception is uncaught and terminates the Node.js process. This can be triggered by a malicious HTTP server sending a small compressed response that decompresses to a size exceeding the limit. The issue affects undici versions >=7.15.0 <7.30.1 and >=8.0.0 <8.12.2. Fixed in versions 7.30.1 and 8.12.2.
Certain versions of the MCP TypeScript SDK and related packages do not limit HTTP POST request body size or JSON-RPC batch length. This allows an attacker to send very large requests or long batches, potentially exhausting server memory and causing denial of service. No authentication is required unless implemented outside the SDK. Fixed versions impose limits on request size and batch length.
CVE-2026-117526 is a code injection vulnerability in reduxjs redux-devtools version 5.0.0. It affects the evalAction function of the Remotedev Server component. The vulnerability allows an attacker with local access to manipulate the action argument to inject code. Public exploit code exists, but the vendor has not yet responded or issued a fix.
The undici WebSocket client, when using HTTP/2 (enabled by default with allowH2: true), crashes the Node.js process if it connects to a malicious server that responds with a failed WebSocket handshake over HTTP/2. This occurs because the client aborts the request too late, leaving an open HTTP/2 stream that emits an unhandled error when the server closes the connection, causing a denial of service. Versions 8.11.0 and 8.11.1 are affected. A fix is available in version 8.11.2. Workarounds include disabling HTTP/2 for WebSocket connections or avoiding untrusted servers until patched.
Nodemailer versions from 3.0.0 up to but not including 10.0.13 contain a vulnerability in the SMTP client where certain regular expressions used to detect SMTP AUTH mechanisms cause quadratic backtracking. This leads to a denial of service by blocking the Node.js event loop during the EHLO response parsing if the server returns a crafted response with long whitespace runs and no matching mechanism. The vulnerability can be triggered pre-authentication by an attacker controlling or influencing the SMTP server or man-in-the-middling the connection before STARTTLS. A fix is available in Nodemailer version 10.0.13.
Nodemailer SMTP client versions from 3.0.0 up to but not including 10.0.10 contain a vulnerability in the SMTP response parser that allows a malicious or compromised SMTP server to cause a denial of service by sending a large number of continuation lines without a completion line. This triggers quadratic CPU usage in the Node.js event loop, freezing the entire process before authentication occurs. The vulnerability is fixed in version 10.0.10.
Artalk versions before 2.10.1 have an unauthenticated server-side request forgery (SSRF) vulnerability. Remote attackers can submit anonymous comments with a crafted page_key parameter pointing to internal URLs. The server fetches these URLs to retrieve page titles without proper validation beyond scheme checking, exposing internal resources via the public comment list. This vulnerability is fixed in version 2.10.1.
Routinator runs out of memory when the JSON output is requested many times concurrently. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP server. Additionally Routinator runs into a stack overflow and exits when a payload item with too much metadata is discarded at once.
This only affects users that make their HTTP or RTR server available to untrusted networks.
A path traversal vulnerability exists in the GiveWP WordPress plugin versions before 4.19.0.1. This flaw allows users with a high-privilege custom role to read arbitrary JSON-parseable files from the server and overwrite the plugin's stored configuration by supplying crafted filenames. The issue is fixed in version 4.19.0.1.
A vulnerability in the Node.js TLS stack allows improper normalization of hostnames containing fullwidth Unicode digits representing IPv4 addresses. This flaw can cause certificate hostname verification to accept a certificate that does not identify the intended peer, enabling potential TLS server impersonation. The issue affects Node.js 24.x and 26.x lines. Exploitation requires an attacker to influence the hostname used for the TLS connection and present a matching certificate, typically requiring privileged network positioning. The vulnerability impacts confidentiality and integrity but does not affect availability. Red Hat has released updated RPM packages to address this issue.
@drone-js-ext/core is a malicious npm package designed for dependency confusion attacks. It impersonates an internal package scope and runs a post-install script that sends host-identifying information over unencrypted HTTP to a third-party server. The package also sends this data each time it is loaded and provides no legitimate functionality.
A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`.
`tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
CVE-2026-116011 is a high-severity vulnerability in CrowCpp's Crow framework before version 1.3.4. It involves uncontrolled recursion in the crow::json::load() function, which can be triggered by sending deeply nested JSON objects. This causes exhaustion of the worker thread stack, leading to server crashes and dropped connections. The issue affects all versions from 0 up to but not including 1.3.4. A fix is available in version 1.3.4.
A vulnerability in graphql-scalars' GraphQLPhoneNumber scalar causes inefficient regular expression complexity leading to exponential backtracking. This can block the Node.js event loop and stall the server when processing certain unauthenticated requests. The issue affects versions from 1.24.1 up to but not including 2.0.1 and is fixed in version 2.0.1.