CVE-2026-42270 is a vulnerability in countly-server, the server-side component of the Countly analytics platform. Prior to versions 24.05.50 and 25.03.44, certain public image and screenshot routes use local filesystem storage and call getStream to pipe filesystem streams to HTTP responses without an error listener. An unauthenticated request with a URL-encoded dot can cause createReadStream to open a directory, triggering an asynchronous EISDIR error that is unhandled, leading to termination of the Node.js process. This results in denial of service by making the analytics API unavailable. The issue affects routes such as star-rating/images/, dashboards/images/screenshots/, /appimages/*, /memberimages/*, and */screenshots/*. The vulnerability is fixed in versions 24.05.50 and 25.03.44.
Node.js HTTP client library undici versions 6.23.0 through 6.29.0, 7.18.0 through 7.30.0, and 8.0.0 through 8.12.1 contain a vulnerability in the fetch() implementation. When a malicious server returns a response with more than five content codings and closes the connection before sending the body, the Node.js process crashes due to an unhandled error. This leads to a denial of service. The issue is fixed in versions 6.29.1, 7.30.1, and 8.12.2, and users should upgrade to these or later versions. No workaround exists.
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 HTTP client library undici versions 4.0.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1 have a vulnerability where the Agent dispatcher silently drops a caller-supplied tls option containing a checkServerIdentity callback due to JSON-based deep cloning. This causes custom TLS certificate verification callbacks to be ignored, potentially allowing acceptance of TLS peers that should be rejected. The issue affects the default dispatcher used by request, fetch, and setGlobalDispatcher, impacting most applications using undici. The vulnerability is fixed in versions 6.29.1, 7.30.1, and 8.12.2 and later.
Node.js HTTP client library undici versions 7.0.0 through 7.30.0 and 8.0.0 through 8.12.1 have a cache poisoning vulnerability when an originless Agent uses redirect and cache interceptors composed in a specific order with a shared cache store. This flaw allows an attacker controlling a redirect target to poison the cache under a trusted URL or disclose private data by serving cached responses to unauthorized users. The issue is fixed in versions 7.30.1 and 8.12.2 by verifying origin consistency and preserving cache-control policies. Users should upgrade or apply recommended workarounds 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 their fetch() implementation's Subresource Integrity (SRI) verification. The algorithm token matching is case-sensitive and only recognizes lowercase tokens, causing valid uppercase or mixed-case tokens to be ignored. This results in the integrity check being bypassed, allowing an attacker controlling the response body to deliver modified content without detection. The issue affects response integrity but not confidentiality or availability. Fixed in versions 7.30.1 and 8.12.2 by normalizing tokens to lowercase before validation.
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.
@casl/ability versions 6.7.5 up to but not including 7.0.2 contain a prototype pollution vulnerability in the rulesToFields() function. This flaw allows attackers who can control rule conditions to modify inherited built-in object properties via specially crafted dotted keys such as 'toString.call'. Exploitation can lead to denial of service of the Node.js process running the affected library.
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.
CVE-2026-103936 is a high-severity vulnerability in the JavaScript libp2p networking stack prior to version 6.0.28. The issue arises in the @libp2p/webrtc webRTCDirect() Node.js listener, which processes unauthenticated STUN Binding Requests before completing peer authentication and connection setup. A crafted short ICE password derived from the STUN request causes an uncaught native invalid_argument exception in node-datachannel or libdatachannel, leading to process termination (SIGABRT). This denial of service vulnerability does not affect confidentiality, integrity, or allow code execution. The issue is fixed in libp2p version 6.0.28.
Red Hat OpenShift Data Foundation 4.17.28 includes a security, enhancement, and bug fix update addressing multiple issues including CA related fixes for NooBaa, Node.js version update, and stability improvements. The update fixes a crash in the noobaa-endpoint caused by an unhandled AbortError from the Azure storage blob library. This advisory addresses several CVEs including CVE-2025-12816 and others, with a high severity rating. No known exploits in the wild have been reported. Users are advised to apply this update after ensuring all previous errata are installed.
Red Hat OpenShift Data Foundation 4.16.36 includes a security, enhancement, and bug fix update addressing multiple issues including Azure Storage Account usage, certificate authority fixes for NooBaa, Node.js version updates, and database error handling. This update fixes several bugs and addresses multiple CVEs including CVE-2025-13465. The update is classified as important and addresses high severity vulnerabilities.
The npm package buyerdashboard@45.3.4 contains malicious code that executes during installation. Its preinstall script runs a Node.js script that sends a request to an external domain with a hardcoded authorization token, disclosing the installing host's public IP and metadata without user consent. The package also depends on a suspicious similarly named package that shadows a core Node module, indicating potential dependency confusion. The package's metadata and versioning suggest it is designed to evade detection and perform unauthorized data exfiltration.
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 from 3.0.0 up to but not including 10.0.10 contain a denial of service vulnerability in the MessageParser.parseHeaders function. This flaw allows attackers to exhaust CPU resources by supplying large recipient lists or long headers that unfold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
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.