The Node.js HTTP client library undici has a cache interceptor vulnerability where unsafe HTTP methods such as POST, PUT, PATCH, and DELETE are improperly cached due to a logic flaw. This can cause state-changing requests to be bypassed by serving cached responses, potentially leading to inconsistent application state. The issue affects undici versions from 7.0.0 up to but not including 7.29.1 and from 8.0.0 up to but not including 8.10.2. Fixed versions 7.29.1 and 8.10.2 prevent caching unsafe method responses while still invalidating cache entries on successful unsafe requests. No workarounds are provided.
A denial of service vulnerability exists in the undici library's WebSocketStream API for Node.js. When a remote peer closes the TCP connection abruptly without performing a proper WebSocket close handshake, the client process crashes. This is due to an unhandled promise rejection triggered by aborting a writable stream while a writer lock is held. The vulnerability affects undici versions from 7.0.0 up to but not including 7.29.1, and from 8.0.0 up to but not including 8.10.2. Patches are available in versions 7.29.1 and 8.10.2. No workaround is currently available.
A vulnerability in the undici WebSocket client for Node.js causes the process to crash when processing a specially crafted permessage-deflate compressed message that exceeds the decompressed payload size limit and contains a malformed DEFLATE block. This triggers an unhandled error in the internal zlib InflateRaw stream, leading to process termination. The issue affects undici versions 6.25.0 through before 6.28.1, 7.28.0 through before 7.29.1, and 8.1.0 through before 8.10.2. No workaround is available, but patched versions have been released.
OpenPanel versions before 2.3.0 contain a code injection vulnerability due to improper validation of chart formula expressions. Authenticated project members with read access can exploit this flaw to execute arbitrary code by leveraging the native JavaScript Function constructor via mathjs matrix objects. This allows attackers to load Node.js built-ins and run operating system commands with the API process privileges, bypassing organization authorization boundaries. The issue is fixed in version 2.3.0.
Improper OCSP response validation in the Snowflake Python, Go, JDBC, and Node.js drivers allowed a revoked TLS certificate to be accepted as valid, because OCSP responses were not reliably bound to the certificate being validated and definitive verification failures were treated as transient. A man-in-the-middle attacker holding a revoked certificate and its private key for a Snowflake or stage hostname could cause the driver to establish a TLS session to the attacker-controlled endpoint anyway, allowing the attacker to read and modify data transmitted within that connection. Successful exploitation requires that on-path position and the corresponding private key, and impact is limited to data carried within the intercepted connection. The fix is available in Snowflake Connector for Python v4.7.3, Snowflake Go Driver v2.2.0, Snowflake JDBC Driver v4.3.4 (including the snowflake-jdbc-fips and snowflake-jdbc-thin), and Snowflake Node.js Driver v3.3.0. Users must manually upgrade.
The npm package taskforge-8xv version 1.2.0 is a malicious runtime loader that fetches and executes JavaScript payloads from a remote origin without any signature or hash verification. It executes the payload in memory by spawning a detached Node.js process with hidden windows and ignored standard IO, enabling stealthy execution. The package maintains state in obfuscated directories and filenames, and terminates prior worker processes before each execution. It provides no legitimate functionality beyond executing remote code, allowing whoever controls the configured origin to achieve full code execution on the host.
The npm package tailwindcss-3d-styles version 1.2.4 contains malicious code that fetches and executes arbitrary JavaScript from an external HTTP server at runtime. This behavior allows remote code execution within the Node.js process of any consumer importing this package. The package masquerades as a legitimate library by copying the upstream tailwindcss-3d code and appending the malicious dropper functionality.
The npm package tailwindcss-animate-styles version 1.0.9 contains malicious code that executes a hidden loader upon require(). This loader decodes a payload that queries public Ethereum RPC endpoints for transactions from a hardcoded wallet, extracts two IPv4 command-and-control (C2) hosts, and fetches XOR-encoded secondary payloads from these hosts. The secondary payloads are executed with full Node.js capabilities, allowing remote code execution with filesystem, network, and process control on the host. After execution, the loader self-erases from the package source to hide its presence.
The tailwind-scrollbar-styles npm package version 4.0.3 contains malicious code embedded in its dist/index.js file. This code executes a base64-encoded payload that queries Ethereum RPC endpoints to retrieve a transaction from a hardcoded Ethereum address. It decodes part of the transaction to obtain a command-and-control (C2) server IP address, fetches and XOR-decodes commands from that server, and executes them via eval and a detached Node.js process. After execution, the malicious code removes itself from the file to evade detection and forensic analysis. This mechanism allows the attacker to dynamically rotate the C2 server by publishing new Ethereum transactions. No patch or remediation information is provided.
The npm package tailwind-container-queries version 0.1.1 contains malicious code that, upon requiring the package, executes an obfuscated payload. This payload queries Ethereum RPC endpoints to retrieve IP addresses, fetches XOR-encrypted code from attacker-controlled servers, decrypts and executes it, and establishes a persistent detached Node.js process on the host. The package impersonates a legitimate Tailwind CSS package by copying its README and repository metadata. After execution, the malicious code removes itself from the package file to evade detection. The attacker can rotate command-and-control IP addresses by publishing new Ethereum transactions, maintaining control over the fetched payloads.
CVE-2026-85063 is a prototype pollution vulnerability in the node-csv package, specifically in csv-parse versions prior to 7.0.2 when using the columns and group_columns_by_name options. An attacker can craft a malicious CSV header containing a duplicate __proto__ field, which leads to modification of the parsed record object's prototype. This can cause unexpected inherited properties to appear in the record, affecting JSON serialization, property enumeration, and type or shape checks. The issue is fixed in version 7.0.2.
toml-node is a TOML parser for Node.js and the browser. Prior to 4.2.0, toml.parse() uses a Peggy 5.1.0 generated recursive-descent parser in lib/parser.js whose peg$parsevalue, peg$parsearray, and peg$parseinline_table_entry functions recurse through nested arrays and inline tables without a depth limit. A remote unauthenticated application parsing an attacker-controlled TOML document containing a few thousand nested arrays or inline tables can exhaust the Node.js call stack, raise an unexpected RangeError rather than the parser's SyntaxError, and terminate an unprotected request worker or process. The corresponding grammar source is src/toml.pegjs, where the generated parser must be bounded. This issue is fixed in version 4.2.0.
toml-node is a TOML parser for Node.js and the browser. Prior to 4.1.2, toml.parse() in lib/compiler.js can be tricked by a table path such as a.b.y.__proto__.__proto__, allowing traversal from a scalar value into Number.prototype and Object.prototype. The currentPath tracking value uses both arrays and strings, so valueAssignments records a comma-joined path such as a,b.y while deepRef checks the dot-joined path a.b.y, allowing the duplicate-key guard to miss and attacker-controlled keys to be written to Object.prototype. A table-array prefix-clearing path in addTableArray can also erase guard state before the same __proto__ traversal. Injected properties become visible throughout the Node.js process and can cause denial of service, logic or authorization bypass, or code execution when an application contains a suitable gadget. This issue is fixed in version 4.1.2.
stream-json is a micro-library of stream components for processing JSON and JSONC with a minimal memory footprint. Prior to 3.5.0, the path filters pick, ignore, filter, and replace in src/core/filters/filter-base.js recompute the full path string from the nesting stack for every checkable token. Because the stack length equals the current nesting depth and a checkable token is emitted at every level, a depth D document costs O(D²) rather than O(D) to process. The issue is triggered by nesting depth rather than byte volume, including the documented pick({filter: 'data'}) traversal-until-match path, so an application that sends untrusted JSON through a string or RegExp filter can block the Node.js event loop and cause denial of service with a small deeply nested document. The streamArray, streamObject, and streamValues streamers are not affected because they use the constant-time asm.depth getter. This issue is fixed in version 3.5.0.
A vulnerability in the Node.js qs library causes qs.stringify to throw a TypeError when serializing an object whose own constructor property has a truthy, non-callable isBuffer member. Red Hat has issued an advisory for Red Hat Hardened Images RPMs, including an update to the grafana13.2 package, addressing this and other vulnerabilities. The update is available and should be applied to affected systems. No active exploitation has been reported.
Since February 2026, there has been a resurgence of attacks abusing Node.js, targeting government, technology, and hospitality sectors. Attackers use the legitimate, signed node.exe binary to execute malicious JavaScript payloads, bypassing signature-based detection. Notable incidents include compromises of an Asian technology company and a U.S. fintech firm, involving advanced techniques such as EtherHiding and deployment of Rust-based backdoors linked to ransomware operations. Multiple attacks involve ModeloRAT, associated with initial access broker Woodgnat, connected to various ransomware families. Attackers combine living-off-the-land tactics with commodity malware and employ ClickFix techniques for initial access.
Microsoft Threat Intelligence observed a sophisticated human-operated campaign exploiting Microsoft Teams external collaboration features to impersonate IT helpdesk personnel. Attackers socially engineer users into granting remote access via legitimate remote monitoring tools. Once established, they deploy malicious MSI packages through PowerShell, staging a portable Node.js runtime and obfuscated JavaScript implant for persistent command execution. The campaign progresses through extensive Active Directory reconnaissance, periodic screenshot captures, and lateral movement via Windows Remote Management toward high-value infrastructure including domain controllers. Unlike commodity phishing operations, this hands-on-keyboard intrusion leverages legitimate tooling throughout, blending malicious activity into normal enterprise operations. The reconnaissance patterns and targeting of identity systems indicate precursor activity consistent with data theft, extortion, or ransomware deployment objectives.
This is a security update for Node.js provided by the SUSE Product Security Team, functionally equivalent to the Red Hat advisory RHSA-2026:62583. The update addresses multiple CVEs including CVE-2026-56846 and related identifiers. No specific affected versions or technical details are provided in the input data.
A security update for Node.js 22 on Red Hat Enterprise Linux 9.6 addresses multiple vulnerabilities including arbitrary code execution, denial of service, server-side request forgery, unauthorized filesystem access, and memory exhaustion. The update fixes issues in components such as SQLite, brace-expansion, ip-address parsing, and HTTP/2 handling. These vulnerabilities could allow attackers to execute arbitrary code, cause crashes, bypass trust boundaries, or exhaust server memory. The update is rated as important by Red Hat Product Security and is available for multiple architectures and Extended Update Support versions.
ApostropheCMS is an open-source Node.js content management system, and sanitize-html provides a simple HTML sanitizer with a clear API. From version 1.9.0 until version 2.17.7, packages/sanitize-html/index.js validates an animation value attribute as one flat URL and does not recognize that attributeName selecting href or xlink:href gives the sibling values, from, to, or by attribute SVG SMIL URL semantics. In configurations that allow the animate, animateColor, animateMotion, animateTransform, or set elements, a values list can begin with a safe fragment and contain a later executable destination that survives allowedSchemesAppliedToAttributes checking. When the sanitized SVG is rendered, the browser can copy that later destination into the live link, and a victim who activates the link can execute script in the application's origin. This issue is fixed in version 2.17.7.