Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to version 3.1.3, several custom-tool components — AgentAsTool, ChatflowTool, and ExecuteFlow — ran code in the in-process vm2 sandbox. To build that code, they inserted a user-controlled baseURL value straight into the JavaScript source, for example const url = "${baseURL}/..."; . The only check on baseURL was isValidURL , but a valid-looking URL can still contain characters that break out of a code string. An authenticated user could craft a baseURL that passed this check, closed the surrounding string, and injected their own JavaScript into the sandboxed script (code injection, CWE-94). The vm2 sandbox runs in the same Node.js process as Flowise and exposes risky dependencies. As a result, the injected code could escape the sandbox and run arbitrary code on the Flowise server as the Flowise process user. Exploitation only requires an authenticated session. The issue is fixed in version 3.1.3, which passes the URL to the sandbox as data instead of inserting it into code and adds stricter URL validation.
A vulnerability in Node.js versions 22.23.1, 24.18.0, and 26.5.0 exists where the dns.resolveAny() function aborts the Node.js process if a DNS response contains more than 256 A records. This can be repeatedly triggered to cause a denial of service condition. The issue is classified as CWE-400, indicating uncontrolled resource consumption. The CVSS v3.0 score is 5.9, reflecting a medium severity impact primarily affecting availability.
CVE-2026-56846 is a high-severity vulnerability in Node.js HTTP/2 handling that allows remote attackers to exhaust memory by evading maxSessionMemory limits through retained header blocks. It affects Node.js versions 22.23.1 and 24.18.0. The flaw results in uncontrolled resource consumption leading to denial of service. No official patch or remediation guidance is currently provided by the vendor.
CVE-2026-58044 is a low severity vulnerability in Node.js HTTP client affecting supported release lines 22, 24, and 26. It involves HTTP request smuggling due to request desynchronization in forwarding proxies that rebuild outbound headers from visible IncomingMessage headers while reusing backend connections. The flaw allows certain headers, including Content-Length, to be omitted from userland header objects but still used internally for HTTP framing, potentially causing inconsistencies.
A vulnerability in Node.js allows a specially crafted spoofed TypedArray byteLength to trigger an assertion failure in synchronous node:zlib APIs, causing the process to crash. This affects all 11 synchronous zlib functions and can be exploited repeatedly to cause denial of service. The issue impacts Node.js versions 22.x, 24.x, and 26.x. No official patch or remediation guidance is currently confirmed.
CVE-2026-58041 is a medium severity vulnerability in Node.js affecting versions 22.x, 24.x, and 26.x. It involves a time-of-check to time-of-use (TOCTOU) race condition in the node:sqlite module, where a stale StatementSyncIterator can continue executing a cached prepared statement after it has been reset and rebound with new parameters. This occurs because SQLTagStore resets cached statements using sqlite3_reset() directly, bypassing the iterator invalidation mechanism introduced in recent releases.
Kiali 2.11.15 for Red Hat OpenShift Service Mesh 3.1 addresses multiple denial of service vulnerabilities related to the node-tar and js-yaml components. These vulnerabilities involve denial of service attacks via crafted gzip bombs, malformed tar archive headers, and crafted YAML documents. The update improves the security posture of the service mesh observability tool by mitigating these issues.
This Red Hat security advisory addresses multiple denial of service vulnerabilities in Node.js 24, specifically in the brace-expansion and node-tar components. The issues include exponential-time complexity in brace-expansion and denial of service via malformed tar archive headers and crafted gzip bombs in node-tar. The update is rated as important by Red Hat and affects Red Hat Enterprise Linux 9 variants. The advisory provides fixes for these vulnerabilities.
Build-Scanner is a heuristic static analysis tool designed to automatically detect common high-impact web application vulnerabilities such as SQL/NoSQL injection, unsafe CORS, weak CSP, and missing CSRF protection in modern React/Node apps. It scans source code quickly without requiring live targets or sandbox environments and can be integrated into CI pipelines as a GitHub Action. The tool is intended to complement, not replace, full SAST/DAST tools and manual review. It flags risky code patterns in Express, Next.js, and Vite/CRA projects. Currently, it is in pre-release and shared for feedback, with no known exploits or patches applicable.
CVE-2026-18446 is a host confusion vulnerability in the fast-uri library used by Red Hat Hardened Images RPMs, including grafana12.4. The flaw arises because fast-uri incorrectly parses URIs when a backslash is used instead of a forward slash to introduce the authority component, differing from Node.js's native URL parser. This discrepancy can allow remote attackers to bypass host-based security policies such as allowlists or SSRF filters, potentially redirecting applications to unintended hosts. Red Hat has released updated RPMs for grafana12.4 to address this issue. No mitigation other than applying the update is currently recommended by Red Hat.
hashi-vault-js is a Node.js module for interacting with the HashiCorp Vault API. Prior to 0.5.2, src/Vault.js concatenates unencoded identifier values including name, username, group, role, and version into Vault request paths and query strings instead of using encodeURIComponent() and URLSearchParams, allowing path traversal and query parameter injection. This issue is fixed in version 0.5.2.
DSSRF is a Node.js library that provides a wide range of utilities and advanced SSRF defense checks. Prior to 1.0.5, is_url_safe can treat localhost as safe when DNS resolver 1.1.1.1 returns NXDOMAIN because dns.resolve4 yields no address and no dns.lookup fallback occurs, allowing server-side request forgery. This issue is fixed in version 1.0.5.
A vulnerability in Node.js affects the permission model enforcement, allowing the process.report feature to write or overwrite files outside the designated --allow-fs-write paths. This flaw can lead to confidentiality issues or bypass the intended security boundaries in affected configurations. The vulnerability impacts Node.js versions 22.x, 24.x, and 26.x. The CVSS score is 3.3, indicating a medium severity level.