CVE-2026-111497 is a high-severity vulnerability in the Google Brotli decoder used in Red Hat AI Base Images and other Red Hat products. It involves an out-of-bounds write triggered by a crafted Brotli-compressed stream, potentially leading to memory disclosure, denial of service, or arbitrary code execution when decompressing untrusted Brotli data. Exploitation requires processing attacker-controlled Brotli data, such as HTTP content with Content-Encoding: br or APIs like Node.js zlib/fetch(). Red Hat platform hardenings increase exploitation difficulty but do not eliminate all impact. No fixes are currently available for Red Hat AI Base Images 3.4.7 (ROCm 6.4).
CVE-2026-120689 is a vulnerability in HDF5 versions prior to 2.3.0 involving uncontrolled recursion in the H5B__iterate_helper() function. This occurs when iterating a version 1 B-tree where a crafted file contains a child pointer that refers back to a node already in the cache, causing unbounded recursion and stack exhaustion. The issue can be triggered by calling H5Gget_info() or H5Gget_num_objs() on a maliciously crafted file, leading to a denial of service (application crash).
CVE-2026-111497 is a security vulnerability in the Google Brotli decoder used by Red Hat OpenShift Dev Spaces and other Red Hat products. It involves an out-of-bounds write triggered by a crafted Brotli-compressed stream, potentially leading to memory disclosure, denial of service, or arbitrary code execution. Exploitation requires decompressing attacker-controlled Brotli data, such as HTTP content with Content-Encoding: br. Red Hat rates this flaw as Important with high attack complexity due to required conditions and platform hardenings. No fix is currently available in the Red Hat OpenShift Dev Spaces 3.31.2 RHEL 10 container release, and users are advised to migrate from devfile v1 to v2 standards and update to supported OpenShift releases. The vulnerability affects Brotli decoder usage in various Node.js and .NET versions depending on whether they use system or bundled Brotli libraries.
CVE-2026-120216 is a vulnerability in the fastify web framework for Node.js versions 5.8.0 through 5.12.7. When configured with a nonzero handlerTimeout, a streaming response that remains open past the timeout causes the server to crash due to an uncaught exception. This results in denial of service by terminating the Node.js process and interrupting other requests. The issue is fixed in version 5.12.8. Users should upgrade or set handlerTimeout to 0 as a workaround.
@fastify/cors versions 8.2.0 through 11.3.x have a vulnerability where using the non-default onSend hook option causes the application to crash on CORS preflight OPTIONS requests. This happens because the plugin re-enters the send pipeline and attempts to write response headers twice, throwing an uncaught exception that can terminate the Node.js process. The issue is fixed in version 11.4.0, which disallows onSend as a hook option and fails registration with a clear error instead of crashing at runtime.
The npm package '@an1mshnpmb9c84920/pipeprobe-obf-m19n5' version 1.0.0 contains malicious code that executes during its 'prepare' lifecycle script. This script runs 'node index.js', which dynamically reconstructs a hostname and performs a DNS lookup to an external domain controlled by the attacker. This behavior confirms code execution on the installer's machine and is concealed by assembling the hostname from string fragments at runtime, evading static detection. The package offers no legitimate functionality related to this DNS callback, indicating malicious intent.
The npm package claims-ac1 version 1.0.0 is a malicious package that collects system information during installation without user consent. It uses dependencies fetched from GitHub tarballs that execute a preinstall script to send details such as Node.js version, home directory, working directory, platform, and architecture to a remote collector host. The package has no legitimate functionality and allows the attacker to change the collector host and code at any time without a new npm release. Machines with this package installed should be considered fully compromised.
A vulnerability in node-i18next prior to version 26.3.4 allows an attacker who can supply resource data to addResourceBundle with deep and overwrite flags both true to overwrite inherited built-in function properties like hasOwnProperty. This can cause process-wide corruption leading to denial of service via TypeErrors. The issue does not affect default usage without deep merging and overwrite enabled and is fixed in version 26.3.4.
A denial of service vulnerability exists in the joi library's string email validation when using the multiple option. The email validation splits input strings using a regular expression that performs in quadratic time on long runs of whitespace, causing the Node.js event loop to block for several seconds with large whitespace inputs. This affects joi versions from 16.0.0 through 17.13.8 and 18.0.0 through 18.3.0. The issue is fixed in joi versions 17.13.9 and 18.3.1.
A vulnerability in the node-forge TLS client causes a crash when the server sends no certificate during the TLS handshake. The client incorrectly checks for the server certificate, leading to a TypeError exception that terminates the Node.js process using the client. This issue is fixed in node-forge version 1.4.1.
A Regular Expression Denial of Service (ReDoS) vulnerability exists in node-forge's pem.decode() function prior to version 1.4.1. The vulnerability arises from inefficient regular expressions used to parse PEM-encoded data, causing the Node.js event loop to block for seconds to minutes when processing crafted inputs. This affects any application that parses untrusted PEM text using node-forge, such as services handling uploaded certificates or keys. The issue is fixed in node-forge version 1.4.1.
node-forge versions prior to 1.4.1 contain a denial of service vulnerability in the BigInteger.modInverse() function due to an infinite loop triggered by negative input values. This occurs when a negative value or modulus is passed, causing the function to spin indefinitely at 100% CPU and block the Node.js event loop. The issue is an incomplete fix of a previous vulnerability and affects RSA key generation when using negative public exponents. The vulnerability does not affect key parsing or standard usage with typical exponents like 65537. It was fixed in node-forge 1.4.1 by returning zero for zero or negative inputs.
A vulnerability in node-forge's TLS implementation allows a denial of service via an uncaught TypeError when processing a TLS record interleaved with a fragmented handshake message. This occurs because the process() function throws an exception after receiving an unexpected record type during a fragmented handshake, terminating Node.js processes using the documented socket wiring. The issue is fixed in node-forge version 1.4.1.
A denial of service vulnerability exists in node-forge's TLS implementation due to recursive processing of TLS records, which can exhaust the call stack. An attacker can send a chunk of thousands of small TLS records (e.g., heartbeat records) before handshake completion, causing a RangeError that terminates Node.js processes using the documented socket wiring. This flaw affects both client and server connections. The issue is fixed in node-forge version 1.4.1 by changing the processing to an iterative approach.
Multiple security vulnerabilities have been identified and fixed in the Node.js 24 module for Red Hat Enterprise Linux 9. These include denial of service issues via unbounded IPv6 parsing and crafted brace patterns, out-of-bounds write in the Brotli decoder, TLS certificate hostname bypasses, DNS hostname truncation, predictable random values, permission and authentication bypasses, and response desynchronization. The update rebases Node.js 24 to the latest upstream release and addresses these security flaws.
@hapi/content versions from 3.0.6 up to but not including 6.0.3 contain a vulnerability in the Content.disposition() function where an unanchored regular expression causes inefficient processing. This can lead to quadratic time complexity when parsing certain Content-Disposition headers with long tokens lacking an equals sign, potentially blocking the Node.js event loop. The issue is fixed in version 6.0.3.