Node.js versions 22.x, 24.x, and 26.x contain a vulnerability in TLS hostname verification where certificates with only a DNS Subject Alternative Name (SAN) can improperly authenticate IP endpoints when clients use non-canonical IPv4 address spellings. This occurs because the function tls.checkServerIdentity() normalizes these IP addresses and matches them against DNS names in the certificate, allowing a certificate with DNS:127.0.0.1 but no IP Address SAN to be accepted for connections to 127.0.0.1. Exploitation requires a trusted CA-issued certificate with a numeric DNS SAN and a platform resolver that accepts non-canonical IP spellings, such as glibc.
Node.js versions 24.22.0 and 26.12.0 contain a vulnerability in TLS hostname verification where certificates without a matching IP address Subject Alternative Name (SAN) can authenticate connections to IPv4 addresses written with non-ASCII characters. This occurs because tls.checkServerIdentity() fails to recognize such hosts as IP addresses, leading to improper validation against DNS names and Common Name fields instead. This flaw is a regression from a previous fix and allows acceptance of certificates with DNS entries like '127.0.0.1' for IP endpoints they were not issued for.
A business logic flaw in Node.js 26.x's zlib.ZipFile API can cause it to return incorrect bytes from a ZIP archive when the local header does not match the central directory. This occurs because a validation error leaves a cached local header without a content offset, allowing attacker-controlled bytes to be returned while CRC-32 verification still passes. This discrepancy can cause Node.js-based ZIP scanners to approve different content than other ZIP implementations.
Node.js versions 22.23.3, 24.22.0, and 26.12.0 contain an improper access control vulnerability in the filesystem permission model. The function fs.realpathSync() lacks required read permission checks, allowing restricted code to bypass intended filesystem read restrictions. This is a partial regression of a previous fix that only covered fs.realpathSync.native().
The @grabcad/preferences-client npm package is a malicious package that acts as a dependency confusion attack vector. It exports a Proxy that returns no-op functions but executes a beacon script on import and post-install, sending sensitive environment information to an attacker-controlled server. This reconnaissance behavior discloses internal hostnames, install paths, and Node.js version to a hostile endpoint. Systems with this package installed should be considered fully compromised, and all secrets and keys must be rotated immediately from a different machine.
A vulnerability in body-parser middleware for Node.js and Express allows a specially crafted request with compressed content to cause an uncaught exception, crashing the application process. This affects versions before 1.20.9 and from 2.0.0 up to but not including 2.4.0. The issue arises because trailing bytes after a valid compressed frame cause an error in the decompression stream that is not caught, leading to process termination. The vulnerability is fixed in versions 1.20.9 and 2.4.0. Users should upgrade or disable request-body inflation as a workaround.
A vulnerability in multer versions 2.0.0 through before 2.5.0 allows a Node.js process to crash when using an asynchronous fileFilter. If a request is aborted while the asynchronous fileFilter is pending, an unhandled error event occurs due to a resumed parsing stream without an error listener, causing the process to exit. This issue is fixed in multer 2.5.0.
A vulnerability in Vite versions 8.2.0 up to but not including 8.3.3 allows an attacker to retrieve the first 4 bytes of files outside the configured server.fs directory by sending a request with the ?vite-wasm-instance query. This occurs because the internal Wasm plugin's load hook reads files without applying server.fs restrictions and exposes the first 4 bytes in error messages when WebAssembly parsing fails. The issue affects setups where the Vite dev server is exposed to the network and is run using Node.js or Deno. A fix is available in version 8.3.3.
The npm package 'log-rotate-testmetest' version 1.0.1 contains malicious code embedded in its binding.gyp file that triggers execution of an obfuscated payload during installation. This payload uses multiple layers of obfuscation including ROT cipher, AES-128-GCM decryption, and brotli decompression, ultimately executing attacker-controlled code via the Bun runtime. The package declares Bun as a runtime dependency to route execution through an alternate runtime rather than Node.js. There is no legitimate native build rationale for this behavior, indicating deliberate malicious intent.
A vulnerability in the Node.js DNS resolver APIs allows hostnames containing embedded NUL characters to be truncated during resolution, potentially causing applications to resolve and act on unintended hostnames. This flaw affects Red Hat Hardened Images RPMs that include Node.js components. Exploitation requires an attacker to supply a hostname with an embedded NUL character to the dns.resolve API, and the application must rely on the resolved records. The issue can lead to confidentiality and integrity impacts comparable to connecting to a wrong host. Red Hat has released updated RPMs addressing this issue.
This entry references multiple vulnerabilities related to Node.js as reported by the Bundesamt für Sicherheit in der Informationstechnik and includes a Red Hat security advisory for updated brotli RPM packages. The advisory addresses security issues in Red Hat Hardened Images but does not explicitly link these updates to Node.js vulnerabilities. No specific affected Node.js versions or detailed vulnerability impacts are provided.
The npm package @worrisome/aaaa contains malicious code that impersonates a Cloudflare Turnstile security check page. When loaded in a browser via an npm CDN, it fetches and decrypts a destination URL and redirects the browser to a runtime-chosen URL. The package does not execute code during installation or require/import in Node.js, so the threat targets end-user browsers loading the HTML through CDNs, not developers or build systems. Computers with this package installed or running should be considered fully compromised, and all stored secrets and keys should be rotated immediately.
CVE-2026-114144 is a high-severity vulnerability in the BinaryMuse toml-node library prior to version 5.0.1. The vulnerability arises because the toml.parse() function converts unbounded long integer strings to BigInt before checking if they fit within the TOML 64-bit integer range. This conversion of very long integer strings consumes super-linear CPU time and blocks the Node.js event loop synchronously, enabling a denial of service (DoS) attack via a crafted TOML document. The issue is fixed in version 5.0.1.
CVE-2026-114143 is a high-severity vulnerability in the toml-node library for Node.js and browsers. Versions prior to 5.0.1 suffer from an inefficient algorithmic complexity issue in the parsing of long dotted keys and table headers, causing quadratic processing time. This can block the Node.js event loop for several seconds or lead to process termination due to memory exhaustion. The maxDepth option does not mitigate this issue. The vulnerability is fixed in version 5.0.1.
CVE-2026-114142 is a high-severity prototype pollution vulnerability in the BinaryMuse toml-node library for Node.js and browsers. Versions prior to 5.0.1 improperly handle quoted key paths during parsing, allowing attacker-controlled properties to be written to Object.prototype. This can cause objects to inherit malicious properties. The vulnerability is fixed in version 5.0.1.
CVE-2026-114141 is a high-severity vulnerability in the toml-node library, a TOML parser for Node.js and browsers. Versions prior to 5.0.1 contain an inefficient algorithmic complexity issue in the addTableArray() function, causing quadratic synchronous processing when parsing documents with many array-of-tables headers. This can block the Node.js event loop and result in a denial of service. The issue is fixed in version 5.0.1.
The npm package test-brotli-testmetest version 1.0.0 contains malicious code that executes during installation. Its install script triggers a node-gyp rebuild that runs an obfuscated JavaScript loader (index.js). This loader decrypts and executes a Brotli-compressed payload, effectively running attacker-controlled code at install time without user visibility. The package was published by the npm account testnewtestme2 on 2026-10-21.
The npm package test-brotli2-testmetest version 1.0.0 contains malicious code that executes during installation. Its install script triggers node-gyp to run an obfuscated JavaScript loader (index.js) that decrypts and executes a Brotli-compressed payload. This payload acts as a credential stealer. The package was published by the npm account testnewtestme2 on 2026-10-21.