A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`127.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered `fs.realpathSync.native()`.
As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
CVE-2026-115895 is a high-severity code injection vulnerability in the happy-dom JavaScript library versions 17.0.0 through 21.0.3. The flaw arises from improper validation of named ESM import aliases, allowing attacker-controlled input to execute arbitrary JavaScript code in the Node.js host process when enableJavaScriptEvaluation is enabled. This vulnerability is a residual issue following an incomplete fix for a previous related vulnerability. The issue is fixed in version 21.0.4.
A vulnerability in graphql-scalars' GraphQLPhoneNumber scalar causes inefficient regular expression complexity leading to exponential backtracking. This can block the Node.js event loop and stall the server when processing certain unauthenticated requests. The issue affects versions from 1.24.1 up to but not including 2.0.1 and is fixed in version 2.0.1.
CVE-2026-106072 is a medium severity vulnerability affecting specific Ubuntu-packaged versions of Node.js. The vulnerability has a CVSS 3.0 score of 6.7, indicating a network attack vector with low attack complexity but requiring high privileges. It impacts confidentiality, integrity, and availability to varying degrees. No detailed description or technical details about the nature of the vulnerability are provided. There are no known exploits in the wild, and no patch or remediation information is currently available.
CVE-2026-106070 is a low severity vulnerability affecting specific Ubuntu-distributed versions of Node.js. The vulnerability has a CVSS score of 3.7 with no confidentiality or availability impact, but limited integrity impact requiring high attack complexity and no privileges or user interaction. No detailed description or technical details about the nature of the vulnerability are available. There are no known exploits in the wild and no patch or remediation information provided.
Node.js versions 22.x, 24.x, and 26.x contain a vulnerability in TLS hostname verification where server certificates can be incorrectly validated against a different IP address when the host is specified as a non-canonical IPv4 literal with leading zeros. This occurs because the hostname normalization interprets leading-zero octets as octal, while the OS resolver interprets them as decimal, potentially allowing a server to be authenticated with a certificate for another IP address.
CVE-2026-105481 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in Node.js HTTP Agent connection reuse affecting versions 22.x, 24.x, and 26.x. It allows a client to accept a response sent before the client has sent the corresponding request due to incomplete handling of unsolicited responses in keep-alive sockets. This flaw is a regression or incomplete fix of a previous vulnerability (CVE-2026-48931).
CVE-2026-105482 is a high-severity vulnerability in Node.js affecting versions 22.23.3, 24.22.0, and 26.12.0. It involves improper access control in DNS resolution functions where hostnames containing a NUL byte are silently truncated, causing dns.resolve*() and dns.reverse() to resolve attacker-controlled names incorrectly. This flaw can lead to applications acting on DNS records for a different hostname than the one validated, potentially bypassing domain allowlists.
A vulnerability in Node.js affects the internal entropy caches used by crypto functions such as crypto.randomUUID(), crypto.randomUUIDv7(), and crypto.randomInt() when user-land startup snapshots or single executable applications are built using snapshots. If these functions are called during snapshot creation, the cached random values are reused across processes started from that snapshot, causing collisions and predictability of supposedly unique identifiers. This impacts Node.js versions 22.23.3, 24.22.0, and 26.12.0.
CVE-2026-106071 is an improper access control vulnerability in Node.js 26.x related to its permission model for filesystem access. The flaw allows access to filesystem paths that do not exactly match a specified wildcard rule due to early termination in the radix tree lookup. For example, a wildcard rule like --allow-fs-read=/etc/passwd.* unintentionally permits reading /etc/passwd. This issue requires the wildcard grant to be directly under the root of the permission tree and differs from CVE-2026-58043. The vulnerability has a low severity score and affects Node.js version 26.12.0.