CVE-2026-14257 is a high-severity vulnerability in the juliangruber brace-expansion library (versions up to 5.0.7) that allows an attacker to cause uncontrolled memory consumption. The expand() function limits the number of results but not their length, enabling crafted inputs with many chained brace groups to exhaust memory and crash the Node.js process with an uncatchable out-of-memory error. This denial-of-service condition cannot be caught by try/catch and results in a fatal process termination. The vulnerability affects applications that pass attacker-controlled strings to brace-expansion.expand(), including via minimatch or glob patterns. A patch has been released that bounds the total output length to prevent unbounded memory growth.
A high-severity vulnerability (CWE-829) in JetBrains WebStorm before version 2026.2 allows arbitrary code execution via the configured Node.js interpreter before project trust is granted. This issue affects local attack vectors without user interaction and impacts confidentiality, integrity, and availability. No official patch or remediation guidance has been provided yet.
CVE-2026-16631 is an OS command injection vulnerability in the publint package-manager Command Handler affecting versions 0.1.0 through 0.1.4. The issue arises from unsafe use of child_process.exec in src/node/pack.js, allowing local attackers to execute arbitrary OS commands. Exploitation requires local access and no user interaction. A patch exists identified by commit adf2d9a09945fc98c85a2520a89f441d78b2dbd8. The maintainer notes that usage with untrusted input is rare.
n8n's JavaScript task runner shared a module cache across all users executing Code nodes, allowing a user to poison this cache and affect other users' Code-node executions on the same runner. This vulnerability breaks user isolation within a single n8n instance but does not enable sandbox escape or remote code execution. It affects all multi-user n8n instances running the JS task runner with built-in or external modules enabled. The issue is fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting access to trusted users, disabling module access in Code nodes, or using dedicated external runners per user or project.
n8n contains a prototype pollution vulnerability in the Edit Fields (Set) node that allows an authenticated user to assign output fields using dot-notation paths without restricting field names. This can corrupt a shared global in the Node.js process, causing all authenticated requests to fail and resulting in an instance-wide denial of service until the process is restarted. The issue is fixed in versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting access to trusted users and monitoring for HTTP 500 errors.
n8n contains a vulnerability where credential-access checks do not validate credentials referenced inside an Execute Sub-workflow node's inline JSON. This allows a user with editor access to a shared workflow to exfiltrate credentials they are not authorized to use by embedding them in the inline sub-workflow JSON. Exploitation requires workflow sharing enabled, editor access, and knowledge of the target credential ID. The issue is fixed in versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting workflow sharing, auditing sub-workflows for credential references, and limiting network egress.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (37bd61826219d14386d02eed926659dfcfcac94d7b414ae6dd6bcdd4a039fab3)
On npm install, the package's postinstall hook (`node test.js`) auto-executes multiple attacker-controlled operations against the installer's machine. (1) `from_str_2` fetches an SSH public key from http://170.205.31.203:3001/api/ssh-key and appends it to `~/.ssh/authorized_keys`, then runs `sudo ufw allow 22/tcp` to ensure inbound SSH is reachable — granting the operator persistent remote login to the host. (2) `from_str_1` recursively walks `process.cwd()` for `id.json` (Solana keypairs), `config.toml`, `Config.toml`, `env`, and `.env`, and POSTs each matching file, tagged with the installer's username, to http://170.205.31.203:3000/api/v1. (3) `from_str_2` also retrieves scan/block filename patterns from http://170.205.31.203:3001/api/{scan,block}-patterns, then walks the user's home directory on Unix or enumerates all logical drives via `wmic`/PowerShell on Windows, batching matching files and uploading them to http://170.205.31.203:3001/api/v1 with username and platform metadata. Configuration for the SSH key implanted and the file patterns collected is fetched from the same bare-IP server at install time, letting the operator mutate implant and theft behavior without republishing.
## Source: ghsa-malware (b2131462e0e7e1b71f5f47819883b4d004ac90ac91377a7e7482ed2b5faa21b7)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
A vulnerability in the @hono/node-server WebSocket adapter allows unauthenticated attackers to cause a memory leak by sending WebSocket upgrade requests with missing or malformed Sec-WebSocket-Key headers. The server retains the request in memory without cleanup, leading to gradual memory exhaustion and denial of service. This affects versions 2.0.0 up to but not including 2.0.10. There is no impact on confidentiality or integrity, only availability.
Red Hat Ansible Automation Platform versions prior to 5.36.00.16 contain multiple security vulnerabilities affecting several components including node-tar, linkify-it, protobufjs, brace-expansion, fast-uri, and DOMPurify. These vulnerabilities are addressed in version 5.36.00.16. The platform is an end-to-end automation solution for system configuration, software deployment, and workflow orchestration. Red Hat has released security advisories and updated images to fix these issues.
Immutable.js versions through 5.1.7 have a denial of service vulnerability due to a hash-collision algorithmic complexity issue in Immutable.Map and Immutable.Set. Attackers controlling keys inserted into these structures can craft many keys with identical 32-bit hashes, causing insertion and lookup operations to degrade from O(1) to O(n) and resulting in O(n²) complexity for building or reading the entire set. This can consume excessive CPU and stall single-threaded runtimes like Node.js, causing denial of service. The issue is fixed in version 5.1.8 by introducing a per-process seeded secondary hash to index large collision buckets, restoring near-linear performance. Workarounds include limiting request body size and object key counts before passing untrusted data to Immutable.js.
A path traversal vulnerability exists in the Node.js Adapter for Hono's serve-static middleware on Windows. An attacker can use an encoded backslash (%5C) in the URL path to bypass prefix-mounted middleware protections and read static files within the configured root directory. The vulnerability does not allow escaping outside the root directory and affects Windows hosts only. It impacts versions prior to 2.0.5 and 1.19.15 of the @hono/node-server package. The vulnerability has a medium severity with a CVSS score of 5.9.
This security update addresses multiple vulnerabilities in SUSE components including cockpit and its related packages. The fixed issues include prototype pollution in lodash functions, SSH command-line argument injection leading to unauthenticated remote code execution, and several denial-of-service vulnerabilities in Node.js packages brace-expansion and minimatch. The update also resolves non-security bugs and introduces various feature improvements and dependency updates.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.12.2, `EnvironmentManager.listBackups()` reads each backup's `_manifest.json` and trusts the manifest's `path` field. `EnvironmentManager.pruneBackups()` later passes that trusted `entry.path` directly to `rmSync(entry.path, { recursive: true, force: true })`. An attacker who can place or modify a manifest inside `data/<env>/.backups/<name>/_manifest.json` can cause `network-ai env backup prune --env <env> --keep <n>` or any code path invoking `pruneBackups()` to recursively delete an arbitrary path accessible to the Network-AI process user. This is fixed in v5.12.2. `pruneBackups()` no longer passes `entry.path` from the on-disk manifest to `rmSync`. The deletion path is recomputed from a format-validated `entry.backupId`, and a `dirname` containment check confines deletion to exactly one level under the backups directory. A poisoned manifest (e.g. `"path": "/"`) is now inert.
Network-AI, a TypeScript/Node.js multi-agent orchestrator, has a shipped, exported, documented feature called `ApprovalInbox` (`lib/approval-inbox.ts`). It is the network surface of the human-in-the-loop Approval Gate, which `ApprovalGate` uses to require explicit human approval for high-risk operations. The HTTP server it exposes has no authentication of any kind and sets `Access-Control-Allow-Origin: *` on every route, including the state-changing `POST /approvals/:id/approve` and `/deny`. As a result, in versions 5.0.0 through 5.12.1, any party who can send an HTTP request to the inbox port — a co-located process, a container/SSRF on the same host, a remote client when the operator binds a non-loopback address, or any website the operator visits in a browser (via the wildcard CORS) — can enumerate pending approvals and approve them, defeating the entire human-in-the-loop control and causing the gated high-risk action (e.g. a shell command the agent was holding for review) to execute without consent. This issue is fixed in v5.12.2. `ApprovalInbox` now accepts a `secret` option. When set, the mutating endpoints `POST /:id/approve` and `POST /:id/deny` require an `Authorization: Bearer <secret>` header, validated in constant time with `crypto.timingSafeEqual`. `startServer()` already binds to `127.0.0.1` by default; operators exposing the inbox on a network must set a secret.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.4.5, the MCP SSE server defaults to an empty secret (`process.env['NETWORK_AI_MCP_SECRET'] ?? ''` at `bin/mcp-server.ts:89`), which causes `_isAuthorized` (`lib/mcp-transport-sse.ts:254`) to return `true` unconditionally for every request — no `Authorization` header is required. Simultaneously, `_handleRequest` sets `Access-Control-Allow-Origin: *` (`lib/mcp-transport-sse.ts:272`) on every response, so a cross-origin browser fetch can read the result without restriction. An unauthenticated attacker who can lure a user to a malicious web page can invoke all 22 exposed MCP tools — including `config_set`, `agent_spawn`, and `blackboard_write` — against a default-configured localhost server. Version 5.4.5 patches the issue.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.12.2, `AgentRuntime` promises scoped file access under a configured sandbox `basePath`, but its path containment checks use raw string prefix tests. A sandbox base such as `/tmp/network-ai-sandbox` also matches a sibling path such as `/tmp/network-ai-sandbox_evil/secret.txt`. An agent/user that can call `AgentRuntime.readFile()` or `AgentRuntime.listDir()` can read or list files outside the intended sandbox when the target path is in a sibling directory sharing the base path prefix. This breaks the documented sandbox boundary. The issue is fixed in v5.12.2. `SandboxPolicy.resolvePath()` and `isPathAllowed()` now use separator-anchored prefix checks (`resolved === base || resolved.startsWith(base + path.sep)`) for both the allow-list and block-list. A sibling directory that merely shares a name prefix (e.g. `/srv/app-evil` vs base `/srv/app`) is no longer treated as in-scope.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.12.2, `EnvironmentManager.backup()` recursively collects files using `_collectBackupFiles()`. `_collectBackupFiles()` uses `statSync(full)`, which follows symlinks. If `data/<env>` contains a symlink to a directory outside the environment root, backup recursion follows the symlink and copies external files into `data/<env>/.backups/<backupId>/`. An attacker who can place a symlink under the environment data directory can cause backup operations to disclose files outside the environment root into backup artifacts. The issue is fixed in v5.12.2. `_collectBackupFiles()` now uses `lstatSync` instead of `statSync` and skips any entry where `isSymbolicLink()` is true. Symlinks are never traversed, so `backup()` can no longer follow a link out of the environment root and copy external files into a backup artifact.
Network-AI is a TypeScript/Node.js multi-agent orchestrator. Prior to version 5.12.2, `EnvironmentManager.restore(env, backupId)` computes the backup path with `join(envDir, '.backups', backupId)` and only checks that this path exists. It does not resolve the result or verify that it remains under `data/<env>/.backups`. A caller can pass a traversal backup ID such as `../../../outside/source-dir` to restore files from an arbitrary directory into the target environment data directory. The issue is fixed in v5.12.2. `restore()` now validates `backupId` against `/^[\w\-]+$/` and asserts `dirname(resolve(join(backupsDir, backupId))) === resolve(backupsDir)` before touching the filesystem. Backup IDs containing path separators or `..` are rejected, so a crafted ID can no longer copy directories from outside `.backups/` into the environment.
A security update for Node.js 22 on Red Hat Enterprise Linux 8 addresses multiple vulnerabilities including cross-site scripting, denial of service, information disclosure, authentication bypass, and trust-policy bypass. These issues affect components such as ip-address, undici HTTP client, Node.js core, and WebCrypto. The update rebases Node.js 22 to the latest release, incorporating fixes for these security flaws.