Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-68613: Authenticated Remote Code Execution via Expression Injection in n8n

Published Dec 19, 2025 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS99.0%100th percentile
CISA KEVYesAdded Mar 11, 2026
In the wildActivePer CISA KEV
Vendor
N8n
IdentifiersCVE-2025-68613CWE-913 · Improper Control of…

CVE-2025-68613 is a critical expression injection vulnerability in the n8n workflow automation platform's workflow expression evaluation system. User-supplied expressions can execute in a context insufficiently isolated from the underlying Node.js runtime, allowing authenticated users with workflow creation or modification permissions to escape expression restrictions and execute arbitrary code with the privileges of the n8n process. The vulnerability affects releases beginning with 0.211.0, with fixes available in 1.120.4, 1.121.1, and 1.122.0 for the corresponding release branches. Successful exploitation can compromise the affected instance, expose sensitive data, and permit unauthorized workflow changes and system-level operations. The vulnerability has a CVSS score of 9.9 and was added to CISA's Known Exploited Vulnerabilities catalog on March 11, 2026.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can cause high-impact losses of confidentiality, integrity, and availability across the affected n8n instance. Attackers may access workflow data, execution history, integration credentials, and other resources accessible to the n8n process; modify workflows and business processes; and perform operating-system operations within the process's permissions. Exposed API keys, database passwords, and OAuth tokens may enable downstream compromise or lateral movement into integrated services. Code execution does not inherently grant root privileges; the scope depends on the process account, deployment isolation, and network access.

Mitigation

If you can’t patch tonight, do this now.

Until upgrading is possible, restrict workflow creation and editing to fully trusted users. Reduce exposure by restricting inbound access and segmenting the deployment. Run n8n under a dedicated non-root account with minimal operating-system permissions, and restrict outbound network access to required destinations. Review workflow changes, unexpected child processes, and unusual outbound connections for signs of abuse. These controls reduce exposure and potential impact but do not eliminate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade to a release containing the fix: 1.120.4 on the 1.120 branch, 1.121.1 on the 1.121 branch, or 1.122.0 or a later release. These updates introduce additional safeguards restricting expression evaluation. Validate critical workflows and integrations after updating. If compromise is suspected, investigate workflow modifications and host activity, rotate potentially exposed integration credentials, and review downstream access logs; patching alone does not reverse an existing compromise.

Public exploits

Exploits

31 exploits validated by Mallory's analysis. Hidden: 20 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.

View more in app →
Blackash-CVE-2025-68613Repository contains a CVE-2025-68613 toolkit targeting n8n (workflow automation) expression-injection leading to RCE. Structure & purpose (4 files): 1) CVE-2025-68613-exploit.py: Standalone Python exploit that uses an authenticated n8n REST API key (X-N8N-API-KEY) to (a) create a minimal workflow with a Set node whose string value is a malicious n8n expression, (b) execute the workflow via /run to trigger evaluation, (c) print returned output, and (d) delete the workflow to reduce artifacts. Payload options include env var leak, whoami/id command execution, reading /etc/passwd, and a bash reverse shell to attacker-controlled IP/port. 2) CVE-2025-68613.py: A “SAFE” remote exposure/version checker (no exploitation) that probes common n8n endpoints (/, /rest/settings, /healthz, /api/v1/health), attempts to detect n8n and parse a semantic version from responses, then compares against vulnerable ranges. 3) CVE-2025-68613.yaml: A Nuclei detection template that requests /signin, /login, or / and extracts a base64-encoded meta tag (n8n:config:sentry), decodes it, derives the n8n version, and flags vulnerable versions using compare_versions logic. 4) README.md: Documentation describing the vulnerability, affected/patched versions, mitigation guidance, and usage examples for the safe checker, nuclei template, and exploit. Overall capability: authenticated network RCE against vulnerable n8n instances by abusing workflow expression evaluation to access Node.js primitives (require('child_process'), require('fs')) and execute OS commands or establish a reverse shell.sahilccras · Disclosed Dec 22, 2025 · Framework: nuclei (template included); standalone python exploit also present · python · yaml · network (authenticated REST API abuse to create/run workflows; expression injection -> RCE) · network (unauthenticated/low-auth version/exposure detection via HTTP GET endpoints; nuclei template and safe checker)WeaponizedCVE-2026-21858Repository purpose: a full-chain exploit PoC for n8n dubbed “Ni8mare”, chaining CVE-2026-21858 (unauthenticated arbitrary file read via Content-Type confusion on a form upload workflow) with CVE-2025-68613 (expression injection sandbox bypass) to achieve remote code execution. Core exploit (exploit.py, Python): - Implements a Ni8mare class that targets a user-supplied base URL and a specific n8n Form Trigger path. - Stage 1 (Unauthenticated AFR/LFI): POSTs JSON to the form endpoint with header Content-Type: application/json and a crafted body containing files[...].filepath, causing n8n to copy/read an arbitrary server-side file and return its contents. - Uses AFR to read /proc/self/environ to discover HOME, then reads $HOME/.n8n/config to extract encryptionKey, and reads $HOME/.n8n/database.sqlite to extract the global:owner (admin) user record. - Stage 2 (Token forge): derives/uses a JWT secret from encryptionKey (forge_token function is present but truncated in provided content) and sets an authenticated session cookie (n8n-auth) for subsequent REST API calls. - Stage 3 (Authenticated RCE): programmatically creates a workflow containing a Manual Trigger and a Set node whose value is an expression-injection payload. The payload uses this.process.mainModule.require to import child_process and run execSync("CMD"), returning command output. Provides --cmd for single command execution and an interactive loop for repeated commands. - Includes a version check via GET /rest/settings and flags vulnerable if version < 1.121.0. Lab environment: - Dockerfile installs n8n@1.65.0 and exposes port 5678. - docker-compose.yml runs n8n with relaxed cookie settings and executes init/setup.sh after startup. - init/setup.sh creates an owner account, logs in, creates and activates a “Vulnerable Form” workflow (Form Trigger with a file field + Respond node responding with the uploaded binary), and prints the vulnerable form URL. Notable targeting constraints (from README and code): exploit is not universal; it requires an existing (or attacker-created, once authenticated) workflow that uses a Form Trigger with file upload and a Respond node configured to return the binary, because the AFR is triggered through that specific request handling path. No evidence of being part of Metasploit/Nuclei/etc.; it is a standalone Python exploit with a dockerized vulnerable lab.Alhakim88 · Disclosed Jan 30, 2026 · python · bash · networkWeaponizedCVE-2026-21858Repository contains a Python exploit (exploit.py) and a Docker-based vulnerable lab for n8n. Core exploit (exploit.py): Implements a full-chain attack labeled “CVE-2026-21858 + CVE-2025-68613” against n8n. It targets a Form Trigger webhook endpoint (user-supplied form path) to perform unauthenticated arbitrary file read by submitting crafted JSON with a fake uploaded file object containing an attacker-controlled “filepath”. Using LFI, it reads /proc/self/environ to discover HOME, then reads $HOME/.n8n/config to obtain the encryptionKey and $HOME/.n8n/database.sqlite to extract the global owner’s id/email/password hash. It then forges an admin authentication token (used as the n8n-auth cookie) and proceeds to achieve RCE by creating/using workflow nodes containing a JavaScript expression payload that escapes to Node.js require() and executes OS commands via child_process.execSync, returning output. The CLI supports: --read PATH (LFI), --cmd CMD (single command), and an interactive command loop. Lab environment: Dockerfile installs n8n@1.65.0 and exposes port 5678. docker-compose.yml runs n8n with N8N_SECURE_COOKIE=false and WEBHOOK_URL=http://localhost:5678/. init/setup.sh waits for /rest/settings, creates an owner via /rest/owner/setup, logs in via /rest/login, creates a workflow with a Form Trigger (webhookId: vulnerable-form) and Respond node, activates it, and prints the vulnerable form URL (http://localhost:5678/form/vulnerable-form). Overall purpose: Provide an operational PoC/full-chain exploit and a reproducible container lab demonstrating unauthenticated file read leading to admin token forgery and remote command execution on vulnerable n8n instances.MOGMUNI · Disclosed Oct 12, 2023 · python · bash · networkOperationalCVE-2025-68613This repository provides a comprehensive research and exploitation toolkit for CVE-2025-68613, a critical expression injection vulnerability in the n8n Workflow Automation platform. The vulnerability allows any authenticated user to execute arbitrary code on the server via crafted workflow expressions, leading to full remote code execution (RCE). The repository includes: - Detailed documentation (README.md, QUICK_START.md, INDEX.md) covering vulnerability mechanics, exploitation, detection, and remediation. - A passive scanner (cve-2025-68613-scanner.py) for safe detection of vulnerable n8n instances without authentication or exploitation. - A Nuclei template (CVE-2025-68613.yaml) for automated authenticated scanning. - A full-featured exploit (exploit_cve-2025-68613.py) supporting six payloads: system info, command execution, environment variable extraction, file read, file write, and reverse shell. The exploit handles authentication, workflow creation, payload injection, execution, and cleanup. The main attack vector is network-based, requiring only low-privilege authentication to the n8n instance. The exploit targets the /rest/login endpoint for authentication, then abuses /rest/workflows and /rest/workflows/{id}/run to inject and trigger malicious expressions. The exploit is operational and provides real-world attack capabilities, including system compromise, credential extraction, and persistence. The repository is well-documented and suitable for both offensive and defensive security teams.TheStingR · Disclosed Dec 22, 2025 · python · yaml · networkOperationalPOC-CVE-2025-68613This repository contains a Python proof-of-concept exploit for CVE-2025-68613, a remote code execution (RCE) vulnerability in the n8n workflow automation platform. The repository consists of two files: a README.md with a brief description, and the main exploit script 'poccve2025-68613.py'. The exploit script allows an attacker to authenticate to a target n8n instance using valid credentials, create a malicious workflow containing a JavaScript expression injection payload, execute arbitrary system commands on the server, retrieve the output, and clean up by deleting the workflow. The script interacts with the n8n REST API endpoints over HTTP(S), specifically targeting '/rest/login', '/rest/workflows', '/rest/workflows/{id}/run', '/rest/executions/{id}', and '/rest/workflows/{id}'. The exploit requires the attacker to know valid credentials for the n8n instance and for the instance to be vulnerable to CVE-2025-68613. The payload leverages JavaScript code injection to execute system commands via Node.js's 'child_process.execSync'. The exploit is operational and provides direct command execution capabilities on the target server.GnuTLam · Disclosed Dec 23, 2025 · python · networkOperationalCVE-2025-68613This repository provides a full proof-of-concept (PoC) and operational exploit for CVE-2025-68613, a remote code execution (RCE) vulnerability in n8n version 0.211.0. The vulnerability arises from insufficient filtering of the 'constructor' property in n8n's expression sandbox, allowing attackers to bypass the intended restriction using bracket notation (e.g., "['constructor']") and ultimately access the Function constructor. The exploit is delivered as a malicious workflow payload (in JSON format) to the authenticated /rest/workflows/run API endpoint. Upon execution, the payload leverages Node.js's child_process.execSync to run arbitrary system commands, such as creating a file in /tmp, thereby demonstrating RCE within the container. The repository includes Docker deployment files, workflow payloads, authentication cookies, and detailed markdown walkthroughs in both English and Chinese. The exploit requires authenticated access to the n8n instance, which can be obtained via password reset or direct database manipulation as described in the documentation. The code is operational and demonstrates real-world impact, but is not weaponized for mass exploitation.111ddea · Disclosed Dec 24, 2025 · json · yaml · networkOperationalCVE-2025-68613This repository contains a Pocsuite3 exploit module (n8n_auth_rce.py) and a detailed README for CVE-2025-68613, an authenticated remote code execution vulnerability in n8n (all versions). The exploit leverages the n8n API to create a workflow containing a malicious Node.js expression, which is then executed to run arbitrary system commands on the server. The script supports both harmless verification (math calculation) and full command execution modes. It requires a valid X-N8N-API-KEY for authentication. The exploit interacts with the n8n API endpoints /rest/workflows (for creation and deletion) and /rest/workflows/{id}/run (for execution). The code is operational and can be used for both detection and exploitation, with automatic cleanup to remove traces. The repository is structured with a single Python exploit file and a README providing usage instructions and technical details.secjoker · Disclosed Dec 24, 2025 · Framework: pocsuite3 · python · networkOperationalCVE-2025-68613This repository contains two Nuclei YAML templates targeting CVE-2025-68613, a critical authenticated remote code execution (RCE) vulnerability in n8n Workflow Automation (versions 0.211.0 - 1.120.3 and 1.121.0). The main exploit template (CVE-2025-68613-exploit.yaml) automates exploitation by authenticating to the target n8n instance, creating a malicious workflow that leverages JavaScript expression evaluation to execute arbitrary code, and extracting system information to confirm exploitation. The exploit requires valid credentials and interacts with several n8n API endpoints to perform login, workflow creation, execution, and cleanup. The detection template (CVE-2025-68613-version-detect.yaml) passively identifies vulnerable n8n instances by probing multiple endpoints and extracting version information using several methods, ensuring high detection coverage. The repository is structured for use with the Nuclei framework, with clear separation between exploitation and detection logic. No hardcoded IPs or domains are present; all endpoints are relative to the target host. The README provides detailed background, usage instructions, and references.intelligent-ears · Disclosed Dec 24, 2025 · Framework: nuclei · yaml · networkOperationaln8n-RCEThis repository contains a proof-of-concept exploit for CVE-2025-68613, a remote code execution (RCE) vulnerability in n8n (tested on version 1.121.0). The exploit is implemented in Python (exploit.py) and requires valid credentials to the target n8n instance. The script authenticates to the target, creates a new workflow with a malicious JavaScript payload that leverages Node.js's child_process module to execute arbitrary system commands, and provides an interactive shell for the attacker. The exploit interacts with several n8n REST API endpoints to perform authentication, workflow creation, payload injection, execution, and result retrieval. The repository also includes a README.md with usage instructions and a requirements.txt specifying the 'requests' library. The exploit is operational, providing a working interactive shell, but is not weaponized for mass exploitation.AbdulRKB · Disclosed Dec 25, 2025 · python · networkOperationalCVE-2025-68613-Python-ExploitThis repository contains a Python exploit script (exploit.py) targeting CVE-2025-68613, a critical remote code execution vulnerability in the n8n workflow automation platform. The exploit abuses insufficient sandboxing in the expression evaluation system, allowing an authenticated attacker to create a workflow with a Code node that executes arbitrary system commands on the server. The script supports both direct command execution and reverse shell payloads, and provides options for different exploitation modes (schedule, webhook, code_node). The exploit interacts with the n8n REST API endpoints for authentication, workflow creation, and execution. The README.md provides a brief description, while exploit.py contains all exploit logic. No detection or fake code is present; this is a functional exploit requiring valid credentials and network access to the target n8n instance.JohannesLks · Disclosed Dec 25, 2025 · python · networkOperationaln8n-exploit-CVE-2025-68613-n8n-God-Mode-UltimateThis repository provides a comprehensive Python-based exploitation framework for CVE-2025-68613, a critical remote code execution (RCE) vulnerability in the n8n workflow automation platform. The main exploit script, 'n8n-godmode-ultimate.py', supports multiple operational modes: detection, safe vulnerability check, proof-of-concept RCE, and full exploitation. It implements several exploitation techniques, including schedule trigger, webhook trigger, code node execution, and expression injection, allowing for flexible attack vectors. The tool can extract the n8n version, perform batch scanning of multiple targets, and, if credentials are provided, exploit the vulnerability to execute arbitrary OS commands, provide an interactive shell, read and write files, extract environment variables, enumerate users and credentials, dump workflows and configurations, and establish a reverse shell. The exploit interacts with the n8n instance over HTTP(S), typically targeting the default web interface at port 5678. The code is operational and provides real exploitation capabilities, not just detection. The repository is structured with a main Python exploit script, a requirements file listing dependencies (requests, urllib3, tqdm, colorama), and supporting documentation. The exploit is intended for authorized security testing and red teaming against vulnerable n8n instances.hackersatyamrastogi · Disclosed Dec 25, 2025 · python · networkOperationalAnalysis-And-POC-N8N-CVE-2025-68613This is a minimal two-file proof-of-concept repository for the alleged n8n CVE-2025-68613 authenticated remote-code-execution issue. `Payload/payload-ssti.js` contains the sole executable artifact: an n8n `{{ }}` expression that reaches Node.js's `child_process.execSync()` through `this.process.mainModule.require()` and executes a placeholder attacker-provided command. `README.md` documents use through the n8n web UI: an authenticated workflow editor adds a Manual Trigger and an Edit Fields (Set) node, inserts the expression, and executes the workflow. The repository does not implement target discovery, authentication, HTTP requests, persistence, reverse shells, or exfiltration. No network, IP, domain, URL, registry, or other target endpoint is embedded in the executable payload; exploitation is performed interactively against the operator's n8n instance.releaseown · Disclosed Dec 25, 2025 · javascript · webOperationaln8n-cve-2025-68613This repository provides a scanner and an authenticated exploit PoC for CVE-2025-68613, a critical expression injection vulnerability in the n8n Workflow Automation Platform (versions 0.211.0–1.120.3 and 1.121.0). The repository contains two main Python scripts: 1. tot-scanner-2025-68613.py: A non-exploit scanner that detects n8n instances, extracts their version, and determines if they are vulnerable. It queries several endpoints (/, /rest/settings, /healthz, /api/v1/health) and supports JSON output for automation. 2. tot-exploit-2025-68613.py: An authenticated exploit that requires valid n8n credentials. It logs in to the target, creates a workflow with a malicious expression in a Set node, and triggers execution to achieve remote code execution. Supported payloads include system info, arbitrary command execution, environment variable dump, file read/write, and reverse shell. The exploit interacts with the n8n REST API endpoints for login, workflow creation, execution, and cleanup. The code is written in Python and uses the requests library. The exploit is operational, providing real RCE capabilities but requiring valid credentials. No hardcoded payloads are present; the user supplies payload type and parameters at runtime. The repository is well-documented, with clear usage instructions and warnings about legal/ethical use.gagaltotal · Disclosed Dec 28, 2025 · python · networkOperationaln8n_CVE-2025-68613_exploit_payloadsThis repository provides payloads for exploiting CVE-2025-68613, a remote code execution (RCE) vulnerability in n8n (a workflow automation tool) when misconfigured with NODE_FUNCTION_ALLOW_BUILTIN=*. The repository contains two files: a README.md with legal disclaimers and a n8nexploit.txt file containing detailed exploitation instructions and example payloads. The exploit leverages the ability to inject JavaScript code into n8n's 'Code > Javascript' workflow node, allowing arbitrary command execution via Node.js's child_process module. Example payloads demonstrate reading system information, listing files, and establishing a reverse shell using netcat. The exploit targets n8n versions below 1.120.4 running in a Docker environment with insecure configuration. No direct network endpoints are hardcoded, but the attacker must specify their own IP and port for the reverse shell. The payloads are operational and require manual insertion into the n8n workflow interface.TheInterception · Disclosed Jan 3, 2026 · javascript · networkOperationalCVE-2026-21858Repository contains a single Python exploit (exploit.py) and a README describing an unauthenticated full-chain RCE against n8n < 1.121.0 by chaining CVE-2026-21858 (content-type confusion leading to arbitrary file read via a public form endpoint) with CVE-2025-68613 (expression injection leading to command execution). Structure & flow: - README.md: documents the attack chain, prerequisites (public form endpoint in an active workflow with file upload + binary response), and usage modes (file read, single command, interactive shell). - exploit.py: implements class Ni8mare that: 1) Targets a user-supplied base URL and form path; uses requests.Session. 2) Performs arbitrary file read by POSTing JSON to the form endpoint with a crafted "files" object containing a chosen "filepath". 3) Reads /proc/self/environ to discover HOME, then reads $HOME/.n8n/config to extract encryptionKey, and $HOME/.n8n/database.sqlite to obtain the user database. 4) Parses the exfiltrated SQLite DB locally (writes to a temp .db file) to locate admin/owner user data (code is partially truncated in provided content but clearly intended to dump/identify admin and derive needed secrets). 5) Forges an admin JWT (stored as cookie n8n-auth) and uses authenticated REST calls (at least /rest/settings is explicit; additional REST endpoints for workflow creation/execution are implied by pwn()/rce() usage). 6) Achieves RCE by constructing workflow nodes (Manual Trigger -> Set) where the Set node value contains a JavaScript expression that calls process.mainModule.require('child_process').execSync("CMD") and returns stdout. Capabilities: - Unauthenticated arbitrary file read (LFI-style) against the form endpoint. - Credential/secret extraction from n8n config and SQLite DB. - Admin token forgery (JWT) and authenticated API interaction. - Remote command execution with output retrieval; supports one-shot commands and an interactive loop. Notable fingerprintable targets/observables: - HTTP GET /rest/settings for version detection. - Form endpoint at <base_url>/<form_path> for the LFI primitive. - File paths: /proc/self/environ, $HOME/.n8n/config, $HOME/.n8n/database.sqlite. - Auth cookie name: n8n-auth. - Node.js execution primitive: child_process.execSync via injected expression.sec-dojo-com · Disclosed Jan 20, 2026 · python · networkOperationalCVE-2026-21858Repository purpose: provides a runnable PoC/operational exploit chain (“Ni8mare”) against n8n combining CVE-2026-21858 (unauthenticated arbitrary file read via Content-Type confusion on a Form Trigger upload flow) and CVE-2025-68613 (expression injection leading to sandbox bypass and RCE). Structure: - exploit.py: main Python exploit. Implements (1) unauthenticated file read by POSTing JSON to a user-supplied form webhook path with Content-Type: application/json and a crafted files[].filepath, (2) discovery of HOME via /proc/self/environ, (3) reading $HOME/.n8n/config to obtain encryptionKey, (4) reading $HOME/.n8n/database.sqlite and extracting the global:owner user record, (5) deriving a JWT secret from encryptionKey and forging an admin session cookie (n8n-auth), and (6) authenticated RCE by creating a workflow with a Manual Trigger and a Set node containing a malicious expression that uses this.process.mainModule.require('child_process').execSync to run arbitrary commands. Provides --read for LFI, --cmd for one-shot command execution, and an interactive command loop. - docker-compose.yml + Dockerfile: builds a local vulnerable lab using n8n@1.65.0 exposed on port 5678, with an init volume. - img/setup.sh: automates lab initialization: waits for /rest/settings, creates an owner, logs in, creates and activates a workflow exposing /form/vulnerable-form with a file upload field and Respond node configured to return the uploaded binary—matching the exploit’s prerequisite. - pyproject.toml: Python packaging/entry point (script name: exploit). Key exploit capabilities: - Unauthenticated arbitrary file read from the n8n host/container filesystem by controlling a file path in the form upload handling. - Credential/material extraction (encryptionKey + SQLite DB) and admin token forging to gain authenticated API access. - Remote command execution via expression injection sandbox escape, returning command output; supports interactive mode. Notable targeting details: - Network target is an n8n HTTP service (commonly :5678). The exploit requires a known, reachable form webhook path (e.g., /form/vulnerable-form) that uses a file upload field and Respond node; without that workflow pattern, the chain may not work (as noted in README limitations).bamov970 · Disclosed Feb 24, 2026 · python · bash · networkOperationalCVE-2025-68613Repository contains a single operational PoC exploit script for CVE-2025-68613 affecting n8n (workflow automation). Structure: (1) README.md documents the vulnerability, affected versions (>=0.211.0 <1.120.4), authentication requirement, and usage examples; (2) poc_final.sh is the entry point. Exploit flow in poc_final.sh: it logs into the target n8n instance via POST /rest/login and stores cookies in /tmp/n8n_session.txt; creates a new workflow via POST /rest/workflows with two nodes (manualTrigger and n8n-nodes-base.executeCommand) where the attacker-supplied command is placed into the executeCommand node parameters; fetches the full workflow JSON via GET /rest/workflows/<id> (needed for 1.x run API); triggers execution via POST /rest/workflows/<id>/run; queries the latest execution via GET /rest/executions?limit=1 to obtain an execution ID; retrieves execution details via GET /rest/executions/<exec_id> and uses an embedded Python snippet to de-reference n8n’s compressed execution data format and print stdout/stderr; finally deletes the created workflow via DELETE /rest/workflows/<id> to reduce artifacts. Primary capability: authenticated remote command execution on the n8n host with output retrieval over the REST API. No persistence or lateral movement logic is included beyond workflow creation and cleanup.h3raklez · Disclosed Mar 3, 2026 · bash · python · network (authenticated HTTP API abuse leading to RCE via workflow creation/execution)OperationalCVE-2026-21858This repository is a standalone exploit/lab for a full n8n attack chain combining CVE-2026-21858 (unauthenticated arbitrary file read via Content-Type confusion on a form upload workflow) with CVE-2025-68613 (expression injection sandbox bypass leading to command execution). The repository contains a Python exploit script, Docker-based vulnerable lab, and a Bash setup script that provisions a vulnerable n8n workflow. Structure: exploit.py is the main exploit entry point. It implements HTTP interaction, arbitrary file read against a supplied form endpoint, SQLite parsing of a downloaded n8n database, and JWT forging for admin authentication. The RCE stage is only stubbed in code, but the README documents the intended JavaScript expression payload using this.process.mainModule.require and child_process.execSync. init/setup.sh configures the local lab by waiting for n8n, creating an owner account, logging in, creating a workflow with a Form Trigger and Respond node, and activating it at /form/vulnerable-form. Dockerfile and docker-compose.yml build and run n8n 1.65.0 with insecure lab settings. Main exploit capabilities: (1) unauthenticated arbitrary file read by POSTing crafted JSON to a vulnerable form endpoint and controlling the file filepath field; (2) extraction of admin id/email/password hash from database.sqlite; (3) derivation of the JWT secret from the encryption key and forging of an n8n-auth cookie; (4) intended authenticated RCE through workflow/expression injection. The implemented code is operational for file read and token forging, while the final command-execution logic is incomplete in exploit.py and described in the README. Notable targets/endpoints include the vulnerable form path, n8n REST API endpoints used by the lab (/rest/settings, /rest/owner/setup, /rest/login, /rest/workflows), and sensitive local files such as /proc/self/environ, $HOME/.n8n/config, and $HOME/.n8n/database.sqlite. Overall, this is a real exploit repository with a working proof-of-concept for the early chain stages and documented end-to-end RCE intent.kaleth4 · Disclosed Apr 9, 2026 · python · bash · web · networkOperationalcve-2026-21858Repository contains a standalone Python exploit plus a Dockerized lab for reproducing a full unauthenticated-to-RCE chain against n8n. The main exploit file is exploit.py, which implements a multi-stage attack: it first abuses CVE-2026-21858 by POSTing JSON with Content-Type: application/json to a user-supplied form endpoint, crafting a fake uploaded file object whose filepath points to arbitrary local files. This yields arbitrary file read from the n8n host. The script then reads /proc/self/environ to locate HOME, reads $HOME/.n8n/config to recover the encryptionKey, and reads $HOME/.n8n/database.sqlite to extract admin-related data. From that material it forges an n8n-auth admin token/cookie and uses authenticated REST API calls to create/trigger a malicious workflow. For code execution, it abuses CVE-2025-68613 by inserting a JavaScript expression payload into a Set node; the payload reaches this.process.mainModule.require, imports child_process, and executes arbitrary shell commands via execSync. The script supports direct file read mode, single-command execution, and an interactive shell loop. Repository structure is small and purpose-built: exploit.py is the operational exploit; init/setup.sh provisions a local vulnerable n8n instance by creating an admin account, logging in, creating a formTrigger + respondToWebhook workflow, and activating it; Dockerfile installs n8n 1.65.0; docker-compose.yml exposes port 5678 and runs the setup script automatically; pyproject.toml defines Python dependencies (requests, pyjwt) and a console entry point; README.md documents the chain, limitations, references, and lab usage. This is not a detection script and not merely a README—it is a functional PoC/operational exploit with a hardcoded but effective RCE payload and a reproducible local lab.Fomovet · Disclosed Jun 21, 2026 · python · bash · web · networkOperationaln8n-cve-2026-21858Repository contains a complete exploit lab and attack chain for n8n, centered on CVE-2026-21858 (unauthenticated arbitrary file read through a vulnerable Form endpoint using JSON Content-Type confusion) and CVE-2025-68613 (expression injection leading to RCE). Structure is small and focused: docker-compose.yml launches a vulnerable n8n 1.65.0 container on port 5678; init/setup.sh waits for the service, creates an admin account, logs in, and provisions an active workflow exposing /form/vulnerable-form with a file field and binary response node; n8n-chain.py is the main exploit; n8n-audit.sh is a detection/audit helper; run.sh automates lab startup and exploit execution. The main exploit script n8n-chain.py implements a multi-stage compromise flow: (1) POST crafted JSON to the form endpoint to coerce the server into reading arbitrary local files; (2) read /proc/self/environ to infer HOME, then read ~/.n8n/config for encryptionKey and ~/.n8n/database.sqlite for admin account data; (3) forge an admin JWT/token using the recovered key; (4) use authenticated access to trigger expression injection with a JavaScript payload that imports Node's child_process and runs arbitrary shell commands via execSync. The script supports file-read mode, single-command execution, interactive shell mode, and generation of an audit script. The repository is a real exploit, not just a README or scanner. It includes an operational payload and a reproducible vulnerable environment, but it is not packaged as a larger exploitation framework. The audit script separately checks version exposure, health, common form paths, and attempts a benign proof read of /etc/passwd, optionally escalating to config key extraction if successful.qianlijaingshan · Disclosed Jul 21, 2026 · markdown · yaml · web · networkOperationalCVE-2026-21858-and-CVE-2025-68613Repository contains two Python exploit scripts, a Docker-based vulnerable lab, and extensive Markdown documentation/reporting for the 'Ni8mare' exploit chain against n8n. The main purpose is to demonstrate and operationalize a pre-auth attack chain combining CVE-2026-21858 (Content-Type confusion leading to arbitrary file read) with CVE-2025-68613 (expression injection / sandbox escape leading to RCE). Structure: README.md summarizes the vulnerabilities, attack chain, affected versions, and lab usage. REPORT.md is a long technical write-up explaining root cause, exploitation flow, and mitigations. ni8mare-lab/ contains a Dockerfile that installs n8n 1.65.0, a docker-compose.yml exposing port 5678, and init/setup.sh which waits for n8n readiness, creates an admin account, logs in, creates a vulnerable Form Trigger workflow with webhookId 'vulnerable-form', and activates it. Exploit capability: ni8mare_exploit.py is the primary Linux/lab exploit. It performs three phases: (1) sends JSON to a form endpoint with a forged files structure to coerce n8n into reading attacker-chosen files; (2) reads /proc/self/environ to locate HOME, then reads ~/.n8n/config and ~/.n8n/database.sqlite, extracts admin data from SQLite, and forges a JWT; (3) uses a malicious JavaScript expression that reaches this.process.mainModule.require('child_process').execSync('CMD') to execute arbitrary commands. It supports file-read mode, single-command mode, and an interactive shell-like loop. ni8mare_exploit_2.py is a variant with extra operator options such as --home for Windows/source-build environments and --token to skip earlier phases. Fingerprintable targets/endpoints: the exploit is aimed at operator-supplied n8n base URLs and form paths, while the lab hardcodes localhost/127.0.0.1:5678 and uses REST endpoints /rest/settings, /rest/owner/setup, /rest/login, /rest/workflows, and /rest/workflows/$ID. Important file targets include /proc/self/environ, ~/.n8n/config, ~/.n8n/database.sqlite, and example /etc/passwd. Overall assessment: this is a real exploit repository, not just a detector or README. It is operational rather than framework-based, with a hardcoded but effective payload chain for arbitrary file read, auth bypass via JWT forgery, and command execution on vulnerable n8n instances.Giangdurian · Disclosed Jul 31, 2026 · markdown · dockerfile · web · networkOperationalPOC-CVE-2025-68613This two-file repository contains a README and a standalone Python proof-of-concept, poc.py, for claimed CVE-2025-68613 in N8N. The script requires a target URL and arbitrary Bash command on the command line, plus a manually populated N8N API key in its global request headers. It creates a workflow with a Schedule Trigger that runs every 10 seconds and a Set node whose raw JSON expression invokes Node.js child_process.execSync on the supplied command. It then activates the workflow, polls the N8N executions API up to five times, and requests execution details with includeData=true to print collected execution data. The repository is not associated with an exploit framework. It is an authenticated RCE exploit rather than a detection-only script; its primary limitations are the required privileged API key and the target's ability to execute the crafted workflow.rmhowe425 · Disclosed Sep 5, 2026 · python · javascript · webOperationalCVE-2025-68613-POCThis repository provides a comprehensive research and exploitation toolkit for CVE-2025-68613, a critical expression injection vulnerability in the n8n Workflow Automation platform. The vulnerability allows any authenticated user to execute arbitrary code on the server via crafted workflow expressions, leading to full remote code execution (RCE). The repository includes: - Detailed documentation (README.md, QUICK_START.md, INDEX.md) covering vulnerability mechanics, exploitation, detection, and remediation. - A passive scanner (cve-2025-68613-scanner.py) for safe detection of vulnerable n8n instances without authentication or exploitation. - A Nuclei template (CVE-2025-68613.yaml) for automated authenticated scanning. - A full-featured exploit (exploit_cve-2025-68613.py) supporting six payloads: system info, command execution, environment variable extraction, file read, file write, and reverse shell. The exploit handles authentication, workflow creation, payload injection, execution, and cleanup. The main attack vector is network-based, requiring only low-privilege authentication to the n8n instance. The exploit targets the /rest/login endpoint for authentication, then abuses /rest/workflows and /rest/workflows/{id}/run to inject and trigger malicious expressions. The exploit is operational and provides real-world attack capabilities, including system compromise, credential extraction, and persistence. The repository is well-documented and suitable for both offensive and defensive security teams.TheStingR · Disclosed Dec 22, 2025 · python · yaml · networkPoCn8n-Authenticated-Expression-Injection-RCE-CVE-2025-68613This repository contains a proof-of-concept (PoC) exploit for CVE-2025-68613, a critical authenticated remote code execution vulnerability in the n8n Workflow Automation Tool (versions >=0.211.0 and <1.120.4). The exploit is implemented as a Bash script ('n8n-cve-2025-68613-poc.sh') that sends a crafted workflow to the target n8n instance via its REST API. The workflow contains a malicious expression that escapes the intended sandbox and executes arbitrary OS commands using Node.js's 'child_process.execSync'. The attacker must supply a valid API key or session for authentication. The README.md provides detailed vulnerability information, usage instructions, and legal warnings. The main attack vector is network-based, targeting the n8n REST API endpoint. The exploit demonstrates both command execution (e.g., 'id') and the potential for a reverse shell. No detection or scanning functionality is present; this is a direct exploitation PoC.mbanyamer · Disclosed Dec 25, 2025 · bash · networkPoCanalysis-and-poc-n8n-CVE-2025-68613This repository provides a proof-of-concept (PoC) exploit for CVE-2025-68613, a critical Remote Code Execution (RCE) vulnerability in the n8n workflow automation platform. The repository contains two files: a JavaScript payload (Payload/payload-ssti.js) and a detailed README.md. The exploit leverages a Server-Side Template Injection (SSTI) vulnerability in n8n's workflow expression evaluation, allowing an authenticated user with workflow edit permissions to execute arbitrary system commands on the server. The payload is a JavaScript expression that, when inserted into a workflow's field, uses Node.js internals to execute a shell command via the 'child_process' module. The README provides comprehensive exploitation steps, affected version details, and mitigation advice. No hardcoded network endpoints or IPs are present in the code; exploitation is performed through the n8n web interface by authenticated users. The exploit is a PoC and does not include weaponized or automated attack scripts.releaseown · Disclosed Dec 25, 2025 · javascript · markdown · networkPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
N8nN8napplication
FAQ

Frequently asked questions

Is CVE-2025-68613 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 11, 2026.
Is there a public exploit for CVE-2025-68613?
Yes. Mallory tracks 31 public exploits or proofs of concept for CVE-2025-68613, the earliest disclosed Oct 12, 2023.
Is there a patch for CVE-2025-68613?
Upgrade to a release containing the fix: 1.120.4 on the 1.120 branch, 1.121.1 on the 1.121 branch, or 1.122.0 or a later release. These updates introduce additional safeguards restricting expression evaluation.
What products are affected by CVE-2025-68613?
N8n.
How severe is CVE-2025-68613?
CVE-2025-68613 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 99.0% (100th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

228 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+64 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity130Community discussion across Reddit, Mastodon, and other social sources.