This security update addresses multiple vulnerabilities in Node.js and related packages on Red Hat Enterprise Linux 9.6 Extended Update Support. The fixes include denial of service issues, cross-site scripting, information disclosure, and authentication bypass vulnerabilities. The update is rated as important by Red Hat and affects the nodejs:22 module and associated components.
A denial of service vulnerability exists in the brace-expansion component used by nodejs-nodemon, due to exponential-time complexity. Nodemon is a development tool that automatically restarts Node.js applications when file changes are detected. This issue can cause nodemon to become unresponsive or crash when processing specially crafted input. Red Hat has issued an important security update addressing this flaw for Red Hat Enterprise Linux 10.0 Extended Update Support.
A vulnerability was found in dresende node-sql-query 0.1.25/0.1.26/0.1.27/0.1.28. Affected by this vulnerability is the function SelectQuery.from/SelectQuery.build in the library lib/Select.js of the component Request Parameter Handler. Performing a manipulation results in sql injection. It is possible to initiate the attack remotely. The exploit has been made public and could be used. Upgrading to version 0.1.29 addresses this issue. The patch is named 3414c42f6de89826fa1f5f36f6139d1e6552778e. Upgrading the affected component is recommended.
The modern-localization npm package versions 1.1.1 and 1.2.1 contain malicious code that fetches and executes arbitrary JavaScript from a third-party mutable key-value store without integrity checks. This behavior occurs via a top-level async function that performs HTTP GET requests to hardcoded jsonbin.io endpoints and executes the retrieved code with full Node.js privileges. Such execution of untrusted code poses a significant security risk, as the package masquerades as a localization library but performs unauthorized remote code execution.
The npm package 'localization-fixer' versions 1.0.1 and 1.1.1 contain malicious code that fetches and executes arbitrary JavaScript from attacker-controlled remote JSON bins. This execution occurs both by writing the payload to a temporary file and running it via child_process.fork, and by dynamically constructing and invoking a function with full Node.js require capabilities. The package masquerades this behavior as a localization synchronization feature, but the remote code execution allows arbitrary code execution on the host system.
`scim-patch`, a library to perform SCIM patch, prior to version 0.9.1 performs prototype pollution when applying a SCIM PATCH operation whose `value` object contains a key like `"__proto__.someProp"`. After one such patch,
`Object.prototype.someProp` is set process-wide, affecting every plain object in the Node process. Any service that calls `scimPatch()` on attacker-controlled JSON (i.e. any SCIM endpoint accepting `PATCH` from an external IdP) is exploitable on a stock Node runtime. Version 0.9.1 contains a patch. A workaround is available. Calling `Object.freeze(Object.prototype)` (and the same on `Array.prototype`, `Function.prototype`) at process startup neutralizes this class of bug — assignment to a frozen prototype becomes a silent no-op in sloppy mode or a `TypeError` in strict mode. Node's `--frozen-intrinsics` flag does this for built-ins automatically.
The npm package @nestjs-passport/jwt contains malicious code disguised as a minimal HS256 JWT helper. It uses heavy JSFuck obfuscation and dynamic code evaluation at import time, executing hidden payloads in the installer's Node.js process. The package is a typosquat of legitimate @nestjs packages and exposes obfuscated private fields inconsistent with normal build outputs. This concealment technique allows arbitrary code execution during module load without readable code paths.
The npm package ts-utility-plus version 1.3.2 contains malicious code that performs an HTTPS request to a hardcoded IP address. The response includes code that is dynamically executed within the Node.js process, enabling arbitrary code execution. The malicious payload masquerades as Font Awesome icon CDN traffic and may deliver a credential or browser secret stealer. This behavior occurs whenever the package's default export function is called.
The npm package tailwindcss-motion-advanced version 1.0.1 contains malicious code that, upon requiring its main entry, queries Ethereum RPC endpoints to retrieve a transaction from a hardcoded attacker address. It extracts IP addresses from the transaction data, fetches an XOR-encoded JavaScript payload over plain HTTP from these IPs, decodes it, and executes it via eval and a detached Node.js process. The package masquerades as a Tailwind CSS plugin but performs unauthorized remote code execution with obfuscated strings and network activity unrelated to its stated purpose.
The npm package eacq-dialog version 35.8.1 contains malicious code that downloads and executes a platform-specific binary from hardcoded external hosts. The payload is saved under disguised filenames in temporary directories, given executable permissions, and launched detached from the Node.js process. The malicious code is triggered both during setup and on every require of the package, using obfuscated string assembly to evade static detection. No integrity checks are performed on the downloaded payload, and the external hosts are unrelated to the package's stated purpose.
The postcss-theme-provider npm package version 1.0.2 contains malicious code that executes upon requiring the package. This code queries public Ethereum RPC endpoints for a transaction from a hardcoded attacker wallet, extracts IP addresses from the transaction data, fetches XOR-encrypted JavaScript payloads from these IPs, decrypts and evaluates them, and then spawns a detached Node.js process to run the payload. The malicious code uses Unicode escapes to obfuscate critical strings such as module names and method calls. The attacker can rotate the command-and-control server by posting new Ethereum transactions, enabling dynamic payload updates.
A vulnerability identified as CVE-2026-55968 affects Apache Thrift Node.js server receive transports, causing a quadratic-time denial-of-service (DoS) condition. This issue impacts versions 3.0 and 4.0 of the affected software. No CVSS score or patch information is provided, and no known exploits are reported in the wild.
An incomplete fix has been identified in Node.js versions 3.0 and 4.0 related to HTTPS Agent TLS session reuse, where hostname verification is skipped. This vulnerability is tracked as CVE-2026-58040 and is associated with CWE-297 (Improper Validation of Certificate with Host Mismatch). No CVSS score or patch information is currently available.
A vulnerability in the Node.js permission model enforcement can cause over-granting of filesystem access across radix-tree prefix boundaries. This flaw affects specific versions of Node.js and may lead to unauthorized access to filesystem resources.
A vulnerability in the Node.js permission model enforcement allows the process.report feature to write and overwrite files outside of its intended scope. This flaw affects specific versions of Node.js and could lead to unauthorized file modifications.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (65aa3700b74bc0d50e4a4ee4fb3b903af0ac2ebea5867a3d1ffd0876647ec2a1)
Package advertises itself as a 2048-style grid game statistics utility, but its declared postinstall hook (`node install-cb.js`) executes on `npm install` and performs behavior unrelated to that purpose. The postinstall shells out via execSync to run `uname -a` and `id`, reads `/proc/1/cgroup` and `/proc/mounts`, inspects Linux capabilities, checks for `/var/run/docker.sock`, and reads the Kubernetes service-account token and namespace at `/var/run/secrets/kubernetes.io/serviceaccount/`. It also enumerates `/`, `/root`, `/root/projects`, performs a host write-test, inspects network configuration, and greps the process environment for variables matching `token|secret|key|password|db_|redis|s3` and related patterns. The collected data (including the k8s SA token length and env keys) is written to `NCODE_ESCAPE.txt` in the current working directory and two parent directories. Author metadata is placeholder-shaped (`merge-tools <merge-tools@example.com>`) and the README/behavior mismatch indicates a cover-story shape. The install-time read of an installer-owned Kubernetes service-account token plus environment secret enumeration constitutes installer-side credential access and container-escape reconnaissance staging.
node-re2 provides RE2 regular expression bindings for Node.js. Prior to version 1.26.1, passing a Buffer whose final bytes form a truncated (incomplete) multi-byte UTF-8 sequence could cause the native binding to read past the end of the allocated buffer while attempting to decode the final, incomplete code point. This could result in an out-of-bounds read and potential disclosure of adjacent memory contents. This issue is fixed in version 1.26.1.