Threat Intelligence Database

n8n is a workflow automation platform. In n8n versions before 1.123.76, 2.37.7, and 2.38.2, the source control push endpoint derived the set of files to push from the file paths and status supplied in the client request payload instead of from the server-side status computed for the requesting user. An authenticated project-scoped user (e.g., a project admin) could therefore reference files belonging to projects they have no access to and push a deletion of those projects' workflows and credentials, resulting in cross-project data destruction. Exploitation requires the Source Control (Environments) enterprise feature to be licensed, enabled, and connected to a remote repository. The issue is fixed in 1.123.76, 2.37.7, and 2.38.2.

n8n is a workflow automation platform. In versions before 1.123.76, 2.37.7, and 2.38.2, the Git node validated a relative remote URL against the configured repositoryPath but then invoked git with that path as its working directory; git walked up to the enclosing repository's top level and resolved the same relative URL from there. An authenticated user (member) who nested the repository one level below the configured path could therefore make an identical URL string pass the file-access check while git resolved it outside the sandbox. A subsequent fetch or pull read a git repository outside N8N_RESTRICT_FILE_ACCESS_TO and merged its objects into the user's own repository, where their contents could be read back. The issue is fixed in n8n 1.123.76, 2.37.7, and 2.38.2, which resolve the remote reference from the directory git actually operates in before applying the sandbox check. As a workaround, the Git node can be disabled by adding n8n-nodes-base.git to NODES_EXCLUDE.

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the OAuth Dynamic Client Registration endpoint bounded redirect_uris but accepted arbitrarily large client_name and grant_types values. An unauthenticated remote caller could repeatedly persist oversized values in oauth_clients and exhaust database storage. The affected validation is in packages/cli/src/modules/oauth-server/oauth-server.service.ts, including MAX_CLIENT_NAME_LENGTH and MAX_GRANT_TYPES. This issue is fixed in versions 2.37.7 and 2.38.2.

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the expression compiler sanitizer resolved through dynamically scoped this and did not reject reserved class member names. A class field named __sanitize could rebind the sanitizer and reach the Function constructor, enabling backend code execution and editor-preview JavaScript execution. The affected AST hook is PrototypeSanitizer in packages/workflow/src/expression-sandboxing.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the /chat WebSocket route accepted a resumeToken and resumed a paused execution without checking that the target node supported chat messages. An anonymous form submitter who received that token could reuse it on the chat route to release a Send-and-Wait, non-chat HITL, or Wait approval gate. The affected authorization logic is packages/cli/src/chat/chat-execution-manager.ts, where canResumeOverChat did not gate the resume target. This issue is fixed in versions 2.37.7 and 2.38.2.

CVE-2026-86078 is a prototype pollution vulnerability in the n8n workflow automation platform. Prior to versions 2.37.7 and 2.38.2, the Instance AI workflow summary function improperly used node names and connection keys from stored workflows as object keys, allowing crafted workflows submitted via the REST API to modify Object.prototype. This could disrupt subsequent requests in the main n8n process. The vulnerability is fixed in versions 2.37.7 and 2.38.2.

CVE-2026-86079 is a path traversal vulnerability in the n8n workflow automation platform affecting Elasticsearch and ElasticSecurity nodes. Prior to versions 1.123.76, 2.37.7, and 2.38.2, these nodes interpolated workflow-controlled identifiers directly into REST request paths without proper encoding. This allowed an attacker to craft identifiers with path separators or dot segments to access unauthorized indices or cluster administration endpoints using stored Elasticsearch credentials. The vulnerability is fixed in versions 1.123.76, 2.37.7, and 2.38.2.

CVE-2026-86080 is a medium severity vulnerability in the n8n open source workflow automation platform. It involves improper verification of cryptographic signatures in the GitHub Trigger node. Prior to fixed versions, the webhook secret was discarded under certain error conditions, causing the system to accept webhook deliveries without proper signature verification. This issue is resolved in n8n versions 1.123.76, 2.37.7, and 2.38.2.

CVE-2026-86081 is a high-severity vulnerability in the n8n workflow automation platform. It involves inefficient regular expression complexity in the Git node clone operation, which uses a regex pattern vulnerable to catastrophic backtracking. An authenticated workflow editor can exploit this to freeze the n8n instance during workflow execution. The issue affects versions prior to 1.123.76, 2.37.7, and 2.38.2 and has been fixed in these versions.

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the public OIDC login and callback endpoints completed authentication even when OIDC was not the enabled active authentication method. An Enterprise administrator who had configured and later disabled an identity provider still exposed a working route that could issue valid sessions. The affected logic is packages/cli/src/modules/sso-oidc/oidc.service.ee.ts, including generateLoginUrl and the callback flow that lacked assertOidcLoginEnabled. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.