The Node.js compression middleware (compression) versions before 1.8.2 have a vulnerability where aborted client connections during compressed responses cause native zlib memory leaks. This can be exploited by a remote unauthenticated attacker to exhaust server memory and cause a crash. The issue is fixed in version 1.8.2, and users should upgrade to this or later versions.
CVE-2026-89259 is a critical vulnerability in the Hugo static site generator affecting versions before 0.165.0. The issue arises because TailwindCSS, included in the default security.exec.allow list, requires highly permissive Node.js execution flags that can bypass intended security restrictions. This allows Node tools invoked during a Hugo build to read and write files outside the project directory. The vulnerability was fixed in version 0.165.0 by removing TailwindCSS from the default allow list. Users not using TailwindCSS or only building trusted sites are not affected. A workaround is to define a restrictive security.exec.allow list in the hugo.toml configuration file.
The Node.js library multiparty, used for parsing multipart/form-data request bodies, contains a denial of service vulnerability in versions from 2.1.0 up to but not including 4.3.1. The parser does not limit the memory used when accumulating headers of a single multipart part, allowing an attacker to exhaust server memory by sending a request with very large header bytes. This vulnerability does not affect confidentiality or integrity. The issue is fixed in version 4.3.1 by capping the size of accumulated part headers.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (cc68c81374c5b78e36fea2f599c5e0004ead6e56dfd02b40cec4f73c62193b30)
The package presents itself as a Tailwind CSS forms plugin (README, repository field, and installation docs are copied verbatim from @tailwindcss/forms) but its sole main module src/index.js is a heavily obfuscator.io-obfuscated Node loader with no CSS-plugin functionality. On require(), the module executes top-level code that installs a createRequire and publishes require, module, and global into named globals (global.r, global.m, global.i, plus several _H/_t_u/_t_s handles) and imports spawn from node:child_process — a stager shape that hands arbitrary execution primitives to code assembled from the rotating string array. It also enumerates public Ethereum JSON-RPC endpoints (drpc.org, publicnode.com, blockscout, blastapi.io) and an Etherscan-like indexer, calls eth_blockNumber / eth_getBlockByNumber / eth_getTransactionCount, and pulls the transaction list for a hardcoded 42-character Ethereum address 0xa322E5f39aDC2490Ef6f0121063eD311D3080e1a, using the returned data as C2 signalling. Results are POSTed with a custom X-Payload-* header to an external endpoint reconstructed from string-array fragments ending in ut.com/api. A CSS plugin has no legitimate reason for obfuscation, node:child_process, or Ethereum RPC traffic; the cover story does not match the shipped code, and the payload runs the moment a developer requires the package.
The Node.js library 'cookies', used by Koa via ctx.cookies, has a Set-Cookie attribute injection vulnerability in versions before 0.9.2. The domain and path options are validated permissively, allowing semicolons and enabling injection of additional cookie attributes. This can override security attributes like SameSite, Secure, HttpOnly, or Domain on cookies issued by the application. The issue is fixed in version 0.9.2 by stricter validation of domain and path values. Applications should avoid using untrusted input for these options as a workaround.
bestzip versions 2.2.6 and 3.0.2 contain an argument injection vulnerability in the nativeZip function that allows attackers to inject arbitrary arguments to the Info-ZIP backend. Attackers can supply a malicious destination path combined with crafted source entries to execute arbitrary commands with Node.js process privileges. Fixed in 2.2.7 and 3.0.3.
cat-sis2go-utils is a dependency-confusion package published against the SIS2GO namespace, with versions inflated to 99.0.0 and 99.1.0. It ships no library code (index.js is an 87-byte stub), and package.json declares both preinstall and postinstall running `node scripts/run.js`, so the payload executes twice during npm install before any application code. The script resolves a DNS canary and POSTs to a webhook.site collector; 99.1.0 additionally sends os.userInfo().username and os.hostname(). The author labels this a PoC, but the beacon fires on any install that resolves the package and exfiltrates a username usable for follow-on attacks, and dependency-confusion packages require incident response even when trivial.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (ad357542f3dd0e1b598ef36d440b1868ac28c6889226864bf799b2f7b6bf5e91)
Package cat-sis2go-utils@99.0.0 declares both preinstall and postinstall lifecycle hooks in package.json that execute scripts/run.js on every npm install. The script unconditionally issues a DNS lookup against d22d92dc-84e5-4b58-8cd6-75bf1ac452c7.dnshook.site and POSTs a JSON beacon containing the installer's hostname and process context to https://webhook.site/d22d92dc-84e5-4b58-8cd6-75bf1ac452c7. The package description self-identifies as a dependency-confusion PoC, and the 99.0.0 version is consistent with a resolution-winning squat targeting an internal package name. Installing the package results in arbitrary code execution on the installer host and fingerprints the machine to third-party out-of-band collectors under the operator's control.
The npm package reactlogo-load version 1.0.0 contains malicious code that executes arbitrary attacker-controlled scripts. Its loadLogo() function extracts a URL hidden in a PNG image using LSB encoding, fetches the code from that URL, and executes it via a reflective Function constructor invocation. The code obfuscates the use of 'constructor' and 'Function' to evade detection. Execution occurs in the Node.js runtime context, granting full access to the host environment. Using this package as documented triggers the malicious code execution, posing a severe risk to any system that includes it.
The npm package express-session-timer versions 1.0.0, 1.0.1, 1.0.11, 1.0.13, 1.0.14, 1.0.15, and 1.0.16 contains malicious code that triggers destructive behavior immediately upon being imported. Approximately 18 seconds after requiring the module, it recursively deletes the <cwd>/src directory and forcibly terminates Node.js processes related to the current working directory. This destructive routine occurs without any user configuration or opt-in and is unrelated to the package's advertised functionality. The package also depends on express-timer pinned to a security-hold placeholder version, indicating prior takedown activity. No patch or remediation information is provided.
The open-item-validator npm package versions 1.0.0 through 1.0.5 contain malicious code that, upon require(), spawns a detached background Node.js process. This process repeatedly fetches JavaScript code over unencrypted HTTP from a dynamic DNS endpoint controlled by an attacker and executes it, allowing arbitrary code execution on the host. The fetch endpoint does not match the publisher's declared homepage, and the package's signature verification does not prevent the attacker from controlling the executed code.
Eclipse Ditto's Node.js JavaScript client versions from 2.0.0 up to but not including 3.8.1, versions 3.9.0 up to but not including 3.9.1, and the predecessor package from 1.0.0 through 2.1.0 have a vulnerability where TLS certificate validation is disabled for WebSocket connections. This allows an attacker who can intercept the connection to present any certificate, bypass validation, and potentially read or alter sensitive protocol messages. Other clients and transports of Eclipse Ditto are not affected.
CVE-2026-84003 is an authentication bypass vulnerability in Microsoft Authentication Library (MSAL) for Node.js. The flaw allows an attacker to perform capture-replay attacks to spoof authentication over a network. Versions from 1.0.0 up to but not including 5.6.0 are affected. A fix is available in version 5.6.0.
CVE-2026-72923 is an uncontrolled resource consumption vulnerability in Microsoft OpenAPI.NET's YAML parsing components. It arises from nested anchors and aliases in YAML OpenAPI documents, which can cause exponential memory allocation during conversion to JSON nodes. This can lead to process termination due to out-of-memory conditions. The vulnerability affects Microsoft.OpenApi.YamlReader versions >=2.0.0-preview.11 and <2.12.0, >=3.0.0 and <3.10.0, and Microsoft.OpenApi.Readers versions <1.6.30. Patched versions are available that impose limits on node count and nesting depth to prevent unbounded expansion. The impact is limited to availability and denial of service; no code execution or data exposure is reported.
SiYuan before 3.8.2 trusts the attacker-writable text/siyuan clipboard MIME type and skips sanitization in the paste handler, allowing code execution in the Node-enabled desktop renderer. Attackers can craft malicious web pages that write to the clipboard, and when pasted into SiYuan, injected scripts execute with full Node.js access through the Electron main process.
Insertion of sensitive information into log files in the Snowflake Python, Go, JDBC, Node.js, PHP PDO, and ODBC drivers allowed authentication tokens, query-result encryption keys, pre-signed cloud-storage URLs, and SAML assertions to be written to diagnostic logs in circumstances where the available log redaction did not cover all affected log paths and data types. An attacker with read access to the log destination, whether the local filesystem, a log aggregation service, or a CI/CD artifact store, could obtain credentials and decryption keys that, if still valid at the time of access, could be used to authenticate to the corresponding Snowflake account or cloud-storage object. Successful exploitation requires read access to the log destination, and impact is bounded by credential lifetime and object scope. 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), Snowflake Node.js Driver v3.3.0, Snowflake PHP PDO Driver v4.2.0, and Snowflake ODBC Driver v3.20.0. Users must manually upgrade and should securely delete previously generated diagnostic logs containing sensitive information where retention is not required.
A denial of service (DoS) vulnerability exists in Multer, a Node.js middleware used in Red Hat Ansible Automation Platform 2.1, caused by processing crafted multipart form data with deeply nested field names. This can lead to excessive CPU and memory consumption, resulting in service unavailability. The vulnerability is rated as high severity by Red Hat. Mitigation involves configuring the 'limits.fields' option in Multer to restrict the number of processed fields, which partially reduces the impact but does not fully prevent the vulnerability. No official fix or patch is currently available.
Multiple security vulnerabilities have been identified and fixed in the Node.js 22 package distributed with Red Hat Enterprise Linux 10.0 Extended Update Support. These include denial of service via memory exhaustion and heap-use-after-free in HTTP/2 handling, unauthorized filesystem access due to permission model enforcement flaws, and server-side request forgery caused by inconsistent IP address parsing. The update addresses these issues to improve the security of Node.js on affected Red Hat platforms.
h3 (npm package) versions <= 2.0.1-rc.14 contain a path traversal vulnerability in serveStatic(). On Node.js deployments, event.url.pathname is not normalized, so percent-encoded dot segments (%2e%2e) are passed to decodeURI() and decoded to ../ sequences without sanitization. An unauthenticated remote attacker can send crafted requests to endpoints served by serveStatic() to read arbitrary files outside the intended static directory. Fixed in 1.15.6 and 2.0.1-rc.15.
Node undici HTTP client library versions >=7.15.0 <7.29.1 and >=8.0.0 <8.10.2 are vulnerable to a denial of service (DoS) attack due to unbounded decompression of HTTP response bodies. The decompress interceptor decompresses responses based on the Content-Encoding header from untrusted sources without limiting the decompressed size, allowing a small compressed payload to expand massively in memory and crash or hang the Node.js process. This vulnerability is fixed in versions 7.29.1 and 8.10.2 by adding a maximum size limit on decompressed output.
Node.js undici library's BalancedPool constructor improperly handles TLS options by deep cloning its options via JSON serialization, which drops function-valued TLS options such as custom checkServerIdentity callbacks. This leads to TLS certificate validation bypass when using BalancedPool with such custom callbacks, allowing acceptance of TLS peers that should be rejected. Other undici components like Client, Pool, and Agent are not affected. The issue is fixed in versions 7.29.1 and 8.10.2.