CVE-2026-58039 is a vulnerability in Node.js affecting versions 22.x, 24.x, and 26.x. It involves improper access control in the Node.js permission model, allowing process.report to write or overwrite files outside the intended --allow-fs-write paths. This flaw can lead to confidentiality impacts or bypass of security boundaries under certain configurations. The vulnerability has a low severity rating with a CVSS score of 3.3.
CVE-2026-68499 is a vulnerability in the node-re2 package, which provides Node.js bindings for Google's RE2 regular expression engine. Versions prior to 1.25.2 have a flaw in the String.prototype.match implementation when using a global RE2 pattern that can match the empty string. This causes an infinite loop due to failure to advance the matching cursor, leading to unbounded native memory growth, blocking the event loop and potentially exhausting host memory. The issue is fixed in version 1.25.2.
re2 provides Node.js bindings for Google's RE2 regular expression engine. Prior to 1.25.2, re2 validates lastIndex against the UTF-8 byte length of a subject but uses it as a UTF-16 code-unit offset in exec, test, match, replace, and split, allowing an attacker-influenced lastIndex on a non-ASCII subject to trigger an out-of-bounds heap read and an uncatchable process crash, with limited heap information disclosure in some cases. This issue is fixed in 1.25.2.
CVE-2026-54722 is a high-severity vulnerability in the dssrf-js Node.js library prior to version 1.0.4. The issue involves improper neutralization of special elements in URL processing, specifically the '@' userinfo delimiter. This flaw allows an attacker to bypass internal IP validation checks, potentially causing a client to access internal services via crafted URLs. The vulnerability is fixed in version 1.0.4.
CVE-2026-58040 is a vulnerability in Node.js versions 22.x, 24.x, and 26.x where the HTTPS Agent's TLS session reuse mechanism skips hostname verification across identity policies. This issue is an incomplete fix of a previous vulnerability (CVE-2026-48934). The vulnerability has a medium severity with a CVSS score of 6.3 and does not have any known exploits in the wild at this time.
CVE-2026-56847 is a vulnerability in Node.js affecting versions 22.x, 24.x, and 26.x. It involves a flaw in the permission model enforcement where the method trace_events.createTracing().enable() can write trace logs outside the intended security boundary when the --allow-fs-write flag is not enabled. This can lead to a confidentiality impact or bypass of intended security controls under certain configurations. The vulnerability has a low CVSS score of 3.3 and does not have known exploits in the wild.
CVE-2026-58043 is a high-severity vulnerability in Node.js affecting versions 22.23.1, 24.18.0, and 26.5.0. It involves improper access control in the Node.js permission model, allowing an attacker with limited filesystem permissions to read or write outside the intended allowed paths due to flawed boundary handling in radix-tree prefix checks.
CVE-2026-56850 is a medium severity vulnerability in Node.js versions 26.x, 24.x, and 22.x. It involves improper authentication due to a flaw in the HTTPS Agent connection reuse mechanism. This flaw can cause PFX object-array key collisions, which may lead to mutual TLS client identities being reused across requests that are configured with different client certificates.
A security advisory from Red Hat addresses multiple vulnerabilities in Red Hat Hardened Images RPMs, including a significant flaw in the Node.js Permission Model (CVE-2026-58043). This flaw allows attackers to bypass permission restrictions, potentially enabling unauthorized read or write access to files and directories within the application's sandbox. The advisory provides updated RPM packages for nodejs24 and related components. No explicit fixed versions are stated, but updated packages are available. The advisory recommends avoiding enabling the Node.js Permission Model by not using the --permission flag to mitigate the vulnerability.
Multiple security vulnerabilities have been identified in Red Hat Hardened Images RPMs for Node.js versions 24 and 26. These vulnerabilities are addressed in updated packages released by Red Hat. The advisories list numerous CVEs affecting these Node.js builds, with fixes included in the updated RPM versions.
Red Hat has issued a security advisory for nodejs24 in Red Hat Enterprise Linux 10 addressing multiple denial of service vulnerabilities. These include a brace-expansion vulnerability causing exponential-time complexity, and two node-tar vulnerabilities allowing denial of service via malformed tar archive headers and crafted gzip bombs. The update is rated as Important by Red Hat Product Security. The advisory provides updated packages to remediate these issues.
Two npm beta releases in the @joyfill namespace were compromised with an import-time JavaScript implant that uses blockchain transactions on Tron, Aptos, and BNB Smart Chain to retrieve encrypted payloads. The malicious code leads to a 77 KB Node.js remote-access trojan identified as DEV#POPPER, which establishes Socket.IO connections for remote control and can execute commands, upload files, read clipboard data, and persist through developer tools. A parallel execution branch downloads additional payloads including an 82 KB Python infostealer assessed to be OmniStealer, targeting browser credentials, Git configurations, and wallet extensions. The compromise affected @joyfill/layouts version 0.1.2-2773.beta.0 and @joyfill/components version 4.0.0-rc24-2773-beta.4, with approximately 16,000 weekly downloads. The loader exhibits exact code overlap with the PolinRider family and DEV#POPPER operations.
IBM Observability with Instana (Agent) versions 1.0.303 through 1.0.320, specifically the IBM Instana Node.js tracer component @instana/core version 6.2.1, contains a prototype pollution vulnerability via its configuration normalization API. This vulnerability allows improper modification of object prototype attributes, which can lead to integrity and availability impacts. The vulnerability has a CVSS score of 7.3, indicating high severity. No official patch or remediation guidance has been provided yet.