Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected. This issue is fixed in version 0.1.1.
CVE-2026-44486 is an information disclosure vulnerability in Axios's Node.js HTTP adapter used in Red Hat OpenShift Virtualization v4.12 images. When Axios is configured to use an authenticated proxy and follows an HTTP redirect, it may inadvertently send the Proxy-Authorization header containing sensitive proxy credentials to the redirected target, potentially exposing these credentials to an untrusted remote server. This issue affects Red Hat products using Axios in Node.js environments with authenticated proxies and automatic redirects enabled. No patch or effective mitigation meeting Red Hat's criteria is currently available.
CVE-2026-102414 is a medium severity vulnerability in the browserify pbkdf2 library up to version 3.1.6. It involves uncontrolled resource consumption due to re-hashing of passwords longer than the digest's block size on every iteration in the JavaScript fallback implementation. This causes a computational cost proportional to the product of iterations and password length, potentially blocking the event loop. The issue affects Node.js versions before 0.12, Bun versions 1.0.0 through 1.1.34 and 1.2.6 and later, and Deno 2.9.0 and later when the fallback is used. Node.js 0.12 and later and browser builds are not affected. Applications that enforce reasonable maximum password lengths are not significantly impacted.
A vulnerability in the OpenSSL QUIC stack used by Node.js allows a remote peer to bypass connection-level flow control for streams. This can lead to excessive memory allocation on the local system, potentially up to 100MB per connection instead of the intended 768 KiB. Exploitation requires specific conditions involving multiple streams and data patterns. The OpenSSL FIPS module is not affected as the QUIC implementation lies outside its boundary. The issue has a CVSS score of 5.3 (low severity) and affects multiple specific Node.js versions. A patch is available to address this vulnerability.
A timing and cache side-channel vulnerability affects SM2 private key operations on ARM64 and RISC-V platforms in certain OpenSSL versions used by Node.js. The scalar point multiplication implementation is not constant-time, which could allow attackers measuring timing or cache patterns during SM2 signing or decryption to gain information about secret scalars. This vulnerability impacts OpenSSL versions 4.0, 3.6, 3.5, and 3.4 but does not affect versions 3.0, 1.1.1, or 1.0.2. Fixes have been released in OpenSSL 4.0.3, 3.6.5, 3.5.9, and 3.4.8. The CVSS score is 3.7, indicating low severity.
A vulnerability in Node.js TLS server occurs when SSL_set_SSL_CTX() is called to switch a SSL_CTX during a handshake and the new context has more provider signature algorithms than the original. This can cause out-of-bounds memory access leading to a denial of service. The issue affects only non-default configurations where SSL_CTX is switched mid-handshake with differing signature algorithms. FIPS modules are not impacted. The severity is low due to limited exploitation scope and the need for specific application behavior.
A vulnerability in the Node.js OpenSSL QUIC stack allows a remote attacker to flood the local QUIC implementation with NEW_CONNECTION_ID frames by bypassing limits on connection IDs. This leads to excessive memory allocation (~400MB) due to improper handling of RETIRE_CONNECTION_ID frames, violating RFC 9000 requirements. The flaw affects multiple Node.js versions and has a CVSS score of 7.5. A patch is available to address this issue.
The npm package hardhat-lock@2.21.0 is a malicious package that impersonates a legitimate logging/middleware library but contains a large, heavily obfuscated payload that executes immediately upon import. This payload grants attacker-controlled code unrestricted access to environment variables, filesystem, and network within the Node.js process. The package misuses the Ethereum tooling keyword 'hardhat' and copies unrelated project documentation to disguise its true nature.
The npm package mini-hardhat version 1.1.4 contains malicious code that masquerades as a JSON logger but actually spawns a detached child process. This child process fetches and executes remote code from an obfuscated URL, enabling arbitrary code execution within the user's Node.js environment. The malicious behavior is engineered to persist beyond the parent process, making it a remote code execution dropper.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (a8e49b1abd7c566b17104c5a2823251df2ca253a0fa509d7c19db1c1942ad13d)
On require, index.js invokes initializeDaemon() at top level, which uses spawn('node', [lib/check-items.js], { detached: true, stdio: 'ignore' }) followed by child.unref() to launch a persistent background process independent of the parent. The daemon HTTP-GETs a JSON payload from the hardcoded endpoint https://game.spawnrealm.com/api/item-realtime?key=abcdef123456 and passes payload.code to `new Function('require', 'module', payload.code)`, executing server-supplied JavaScript inside the installer's Node process with full `require` access. An RSA signature check is performed against a public key bundled in the package (crypto-config.js), so the author controls both the signing key and the verifier and the check provides no independent integrity guarantee. Anyone controlling game.spawnrealm.com — including via DNS or TLS — can run arbitrary code as the installing user for the lifetime of the host process. The package is advertised as a validator library, and this remote-code-loader behavior is undisclosed and unrelated to the stated purpose.
A denial of service (DoS) vulnerability exists in the Angular Server-Side Rendering (SSR) package @angular/platform-server due to a flaw in the domino HTML parser. When processing untrusted input containing an incomplete DOCTYPE declaration ending with whitespace before EOF, the parser enters an infinite synchronous loop that consumes 100% CPU and freezes the Node.js server process. This affects applications that bind untrusted user input to [innerHTML] or manipulate DOM on the server. The vulnerability is exploitable remotely without authentication. Workarounds include avoiding direct binding of untrusted input to [innerHTML] or sanitizing input to reject incomplete DOCTYPE strings. A patch is available for affected versions.
The fast-uri library has a vulnerability where it accepts hosts with unbalanced or misplaced brackets in the URI authority without error. This can cause discrepancies between the host parsed by fast-uri and the host resolved by Node.js URL clients, potentially leading to security bypasses in host-based access controls. The issue is fixed in fast-uri versions 2.4.6, 3.1.7, and 4.1.4.
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.2.4 and 12.0.2, a single message with a deeply nested object in its pattern can terminate a NestJS microservice using the TCP or RabbitMQ transport. ServerTCP#handleMessage and ServerRMQ#handleMessage pass a client-controlled non-string pattern to JSON.stringify to derive the handler lookup key; sufficiently deep nesting throws RangeError: Maximum call stack size exceeded, and the unhandled promise rejection terminates Node.js under its default behavior. An attacker who can reach the TCP port or publish to the consumed RabbitMQ queue or exchange can crash the service on demand; other transports are not affected because their patterns arrive as strings. This issue is fixed in versions 11.2.4 and 12.0.2.
CVE-2026-102278 is a high-severity vulnerability in the juliangruber brace-expansion library. It involves uncontrolled recursion in the expand_() function when processing deeply nested brace groups, which can exhaust the native stack and cause the Node.js process to terminate. This leads to a denial of service condition. The issue affects multiple versions prior to 1.1.20, 2.1.6, 3.0.8, and 5.0.11, where the recursion occurs at comma-member and single-set expansion sites. The vulnerability is fixed in these versions.
CVE-2026-102277 is a medium severity vulnerability in the juliangruber brace-expansion library that causes uncontrolled resource consumption. The expand function in affected versions repeatedly rescans input patterns with many trailing closing braces, leading to quadratic CPU and memory usage. This results in a recoverable denial of service by blocking the Node.js event loop. The issue is fixed in versions 1.1.21, 2.1.7, 3.0.9, and 5.0.12.
The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.
CVE-2026-101916 is a high-severity vulnerability in grpc-node's @grpc/grpc-js library where improper certificate validation occurs. Versions prior to 1.13.6 and between 1.14.0 and before 1.14.5 do not properly distinguish authorized from unauthorized peer certificates when server credentials have requireClientCertificate set to false. This can cause applications to mistakenly treat unauthorized certificates as authorized, leading to improper authentication. The issue also affects @grpc/grpc-js-xds when RBAC authentication is enabled. The vulnerability is fixed in versions 1.13.6 and 1.14.5.
The llm-nebula npm package version 1.0.0 contains a malicious preinstall script that executes automatically during installation. This script is heavily obfuscated and runs with the user's privileges, enabling arbitrary filesystem, process, and network operations. The package pretends to be a legitimate LLM SDK but includes a runtime decoder that dynamically resolves Node.js built-in modules and commands, allowing remote code execution at install time.
Axios versions from 1.13.0 up to but not including 1.20.0 have a vulnerability in HTTP/2 session initialization where inadequate error handling for ClientHttp2Session errors can cause unhandled exceptions. This can lead to the termination of the Node.js process and result in denial of service. The issue is fixed in version 1.20.0.
Axios versions from 1.15.2 up to but not including 1.20.0 have a vulnerability in the Node HTTP adapter where request options lack a dedicated createConnection property. This allows an attacker to exploit a prototype pollution flaw by placing a malicious createConnection function on Object.prototype. The attacker-controlled function can intercept and manipulate HTTP request headers and bodies, including credentials, while the URL appears legitimate. The issue is resolved in version 1.20.0.