Zolbooo

A path-traversal issue exists when a specially crafted non-string object is passed to the `moment.locale()` function. The internal guard assumes the input is a string; however, an object with a `match()` method that satisfies the check and a `toString()` method that returns a traversal path can reach an internal `require()` call with attacker-controlled path segments. This primarily affects server-side npm users who pass user-provided input directly to the function.

The software exposes the shared Buffer pool of Node.js to sandboxed code. This allows sandboxed code to acquire ArrayBuffers from small allocations to read and write to host-realm buffers. This issue can lead to the disclosure of host memory used by `Buffer.from`, `Buffer.concat`, and related allocations, resulting in sensitive data exposure and potential denial-of-service.

A sandbox escape exists when running on Node.js 26. The issue occurs because `WebAssembly.compileStreaming` and `WebAssembly.instantiateStreaming` can produce a raw host-realm Promise that rejects with a host-realm error object. By controlling `Symbol.species` via `Promise.prototype.finally`, sandbox code can obtain this raw host error, navigate from the host error constructor to the host Function constructor, and recover the host `process` object. This allows the attacker to gain host Node.js capabilities, such as access to host modules like `fs`, within the process running the sandbox. This escape is possible using a default `new VM()` sandbox and does not require NodeVM, require permissions, host object injection, or any unsafe configuration.

An authenticated user with permissions to create and execute workflows can achieve a sandbox escape within the JavaScript Code node. This occurs because the VM sandbox fails to freeze the `Function.prototype`, enabling the user to pollute it during execution and recover a reference to the host's `globalThis`. The successful execution of this exploit chain requires specific modules to be configured as allowlisted imports in the deployment.

n8n is an open-source workflow automation platform. An authenticated user with permission to create or modify workflows can exploit crafted expressions in workflow parameters to trigger system command execution on the host running n8n. This allows for potential full server compromise, including the theft of API keys, credentials, and secrets. The issue stems from an expression escape vulnerability and incomplete AST-based sanitization. Public exploits are available.

Lodash versions 4.17.23 and earlier are susceptible to prototype pollution through the ` .unset` and ` .omit` functions. The initial fix did not fully address the issue, as an attacker can bypass the check by using array-wrapped path segments. This allows for the deletion of properties from built-in prototypes like Object.prototype, Number.prototype, and String.prototype. The issue allows deletion of prototype properties but does not permit overwriting their original behavior.