hashi-vault-js is a Node.js module for interacting with the HashiCorp Vault API. Prior to 0.5.2, every API method in src/Vault.js passes failed requests through parseAxiosError(), which rethrows the raw AxiosError while retaining AxiosError.config and the equivalent response configuration. These objects can contain the X-Vault-Token request header and err.config.data request body, including submitted passwords or secret values. When a consuming application records the caught exception through console logging, structured loggers, monitoring, crash reporting, or an application performance monitoring service, the live Vault token and request secrets can be stored in plaintext and exposed to anyone with access to that output. A stolen token can permit unauthorized access to the Vault instance under the token's policies. This issue is fixed in version 0.5.2.
The sm-crypto JavaScript library for Chinese cryptographic algorithms SM2, SM3, and SM4 has a critical vulnerability in versions prior to 0.5.0. The default key generation in Node.js uses a cryptographically weak pseudo-random number generator seeded from Math.random() and the current time, allowing attackers who can observe Math.random() outputs and estimate key generation time to recover private keys and forge signatures. This issue is fixed in version 0.5.0.
A memory leak vulnerability exists in honojs node-server versions prior to 2.0.10. When a WebSocket upgrade request with a missing or malformed Sec-WebSocket-Key header is sent to an upgradeWebSocket route, the IncomingMessage object is retained indefinitely due to a missing cleanup path. This allows an unauthenticated attacker to cause unbounded memory growth and potentially make the service unavailable. The issue is fixed in version 2.0.10.
Hub is a Node.js WebSocket server and client with added features. Prior to 0.2.16, every incoming unauthenticated WebSocket connection triggers loadDefaultConnectionEventListeners to call requestClientId, which calls rpc.send for the get-client-id action and pushes a request into RPC.requests. The RPC.waitForReply function starts a setInterval polling loop every 10 milliseconds that is cleared only after a matching reply; if the client remains silent and closes, the timer and pending request stay allocated because the socket close path does not cancel them. Repeated connections therefore cause unbounded timers and heap entries, exhausting CPU and memory and making the server unavailable. This issue is fixed in version 0.2.16.
OpenClaw CLI contains a path traversal vulnerability in its canvas tool's a2ui_push action, allowing authenticated users to read arbitrary files on the gateway filesystem. The vulnerability arises because the jsonlPath parameter is used directly in a file read operation without any path validation or restriction. This can lead to sensitive information disclosure, such as reading system files or credentials. A proof-of-concept demonstrates reading /etc/passwd and exfiltrating its contents to a connected node client. A patch is available for this issue.
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.28 have a vulnerability where the host environment sanitizer misses two Node.js control variables. This allows lower-trust environment sources, such as workspace .env files or tool overrides, to pass these control variables through the sanitizer. The issue affects the environment of Node.js child processes launched under certain configurations, potentially influencing their behavior. The vulnerability does not alter the trusted-operator model of OpenClaw. A fix is available starting with version 2026.5.26. Mitigations include avoiding untrusted environment inheritance and restricting access through allowlists and disabling the affected feature if not needed.
A critical Denial of Service (DoS) vulnerability exists in marked version 18.0.0 through before 18.0.2. By supplying a crafted 3-byte input sequence (tab, vertical tab, newline), an unauthenticated attacker can trigger infinite recursion in the parser's tokenizer, causing unbounded memory allocation and crashing the Node.js application due to out-of-memory (OOM). This affects any application using marked to parse untrusted input. A fix is available in version 18.0.2.
urllib3, when used in a Pyodide runtime environment such as browsers or Node.js, does not enforce its redirect control parameters (`retries` and `redirect`). This is because the runtime itself controls redirect behavior, ignoring urllib3's settings. This can lead to applications relying on urllib3 for redirect control remaining vulnerable to SSRF or open redirect attacks if they depend on disabling redirects. A patched version of urllib3 is available for Node.js usage, but browsers inherently lack mechanisms to control redirects via XMLHttpRequest or the Fetch API, resulting in default redirect behavior.
auth-fetch-mcp is an MCP server that lets AI assistants fetch content from authenticated web pages. Version 3.0.1 implements SSRF protection in `assertSafeUrl()` (`src/security.ts`) to block requests to private and loopback addresses. However, the `isPrivateV6()` function fails to detect IPv4-mapped IPv6 loopback addresses in their hex-normalized form. When an attacker supplies a URL such as `http://[::ffff:127.0.0.1]:PORT/`, the Node.js WHATWG URL parser silently normalizes the host to `[::ffff:7f00:1]`. Because `net.isIPv4('7f00:1')` returns `false`, the private-IP check is bypassed and the URL is passed to the browser or HTTP client, allowing the MCP tool to reach loopback services that are supposed to be blocked. The issue is exploitable under default configuration without any special environment variable. Version 3.0.1 patches the issue.
Multiple security vulnerabilities have been identified in the Node.js 22 module for Red Hat Enterprise Linux 8, including arbitrary code execution, denial of service, and server-side request forgery. These issues affect components such as SQLite, brace-expansion, and ip-address parsing libraries. Red Hat has released an important security update addressing these flaws.
Prompty is a markdown file format (.prompty) for LLM prompts. Prior to 0.1.5 and 2.0.0-beta.5, the TypeScript Nunjucks renderer evaluated untrusted .prompty template bodies with unrestricted JavaScript member access. An attacker-controlled template could traverse constructor and prototype properties to execute JavaScript in the host Node.js process. This issue is fixed in versions 0.1.5 and 2.0.0-beta.5.
envpack-conf version 1.0.1 is a trojanized npm package impersonating the legitimate pkg-conf utility. It contains malicious code that, when imported, asynchronously queries multiple public Ethereum RPC endpoints for transactions from a specific attacker address. It decodes transaction data to retrieve two IPv4 addresses, fetches an XOR-encrypted second-stage payload from these hosts, decrypts it, and executes it both via eval() and a detached Node.js child process. The package uses obfuscation techniques such as Unicode escapes and typosquatting to evade detection and impersonate the original maintainer.
Seerr is an open-source media request and discovery manager for Jellyfin, Plex, and Emby. Prior to version 3.4.0, Seerr's ImageProxy in server/lib/imageproxy.ts uses the upstream ETag and Content-Type response headers to build a cache filename for the unauthenticated GET /avatarproxy/:jellyfinUserId route, allowing a malicious or compromised Jellyfin or Emby server, or a man-in-the-middle attacker on a plaintext media-server connection, to supply traversal sequences that path.join and fs.writeFile normalize outside the cache directory, overwrite /app/dist/index.js or other files, and execute code as the node user after a container restart. This issue is fixed in version 3.4.0.
A vulnerability in the brace-expansion npm package's expand() function can lead to excessive memory consumption and cause a denial of service (DoS) by crashing the Node.js process with an out-of-memory error. This flaw affects applications that pass attacker-controlled input to brace-expansion directly or indirectly via minimatch or glob. The vulnerability is primarily a concern during build or development tooling, as brace-expansion is typically not exposed to untrusted network input in most Red Hat products.
The npm package @assetshop/verify-cli versions 99.0.0 and 99.0.1 contains malicious code that executes during installation. Its preinstall script collects system and user information such as username, hostname, platform, architecture, current working directory, home directory, and Node.js version. This data is then transmitted via HTTPS and DNS requests to a hardcoded external callback domain. This behavior is consistent with dependency confusion reconnaissance techniques used to verify internal package name resolution against private registries.
The npm package 'egypt0811' version 1.0.0 contains a malicious index.html file that acts as a redirect page styled like a Cloudflare Turnstile interstitial. It includes obfuscated JavaScript that redirects browsers to a phishing or malicious destination URL. The package does not execute code during installation or require-time and does not contain Node.js modules or lifecycle scripts. This behavior indicates registry abuse to host a phishing redirect page rather than a direct supply-chain attack on developers. Any system with this package installed should be considered compromised, and secrets should be rotated immediately.
The mnteckets npm package versions 1.0.0 and 1.0.1 contain malicious content designed to redirect users who open the included HTML file in a browser to a phishing site. The package does not execute code during installation or require/import in Node.js, but the HTML file mimics a Cloudflare Turnstile challenge and performs an obfuscated redirect upon user interaction. This behavior indicates the package is a registry-hosted phishing or redirect threat rather than a traditional supply-chain attack. There is no confirmed patch or fix available.
The mobicommn npm package version 1.0.0 contains malicious code in the form of an index.html file that mimics a Cloudflare Turnstile challenge. This HTML file, when loaded in a browser, reconstructs a URL from an obfuscated string and redirects the user. The malicious code does not execute during npm install or when the package is imported in Node.js, as Node does not execute HTML files. However, if the HTML file is opened in a browser, it can trigger the redirect. The package is considered fully compromising to any system where it is installed or running, with a recommendation to rotate all secrets and keys from a different machine and remove the package. There is no confirmed patch or fix available at this time.