CVE

CVE-2025-68613 — Critical RCE in n8n Workflow Automation

What Is n8n and Why This Vulnerability Matters

n8n is a Node.js-based workflow automation engine that lets teams orchestrate integrations, APIs, data pipelines, and business logic through configurable workflows. These workflows often:

• Access internal services and APIs.
• Store and process credentials and secrets.
• Automate privileged operational tasks.
• Bridge external SaaS platforms with internal systems.

This makes n8n a high-value target. When compromised, attackers inherit its trust relationships rather than merely breaching an application.

CVE-2025-68613 at a Glance

• Vulnerability type: Remote Code Execution (RCE)
• Severity: Critical (CVSS 9.9)
• Attack vector: Authenticated
• Affected versions:n8n ≥ 0.211.0 and < 1.120.4 / 1.121.1 / 1.122.0
• Impact: Arbitrary command execution on host

While authentication is required, many deployments grant workflow editing permissions broadly, making compromised accounts or insider threats especially dangerous.

When workflow logic can execute system commands, every automation user becomes a potential attacker.

Root Cause: Unsafe Expression Evaluation

n8n allows users to embed dynamic expressions inside workflows to compute values at runtime. In vulnerable versions, these expressions were evaluated in an insufficiently sandboxed execution context. As a result, attacker-controlled expressions could:

• Escape the intended execution scope.
• Access Node.js runtime internals.
• Invoke system-level functions.
• Execute arbitrary OS commands.

This converts workflow configuration into an execution primitive.

High-Level Exploitation Flow

Exploiting CVE-2025-68613 does not require complex chains:

1. Gain authenticated access to n8n.
2. Create or modify a workflow.
3. Inject a malicious expression.
4. Trigger workflow execution.
5. Achieve remote code execution.

From there, attackers can establish persistence, pivot internally, or exfiltrate sensitive data.

Real-World Impact

• Complete server takeover.
• Exposure of API keys, secrets, and credentials.
• Workflow manipulation and logic poisoning.
• Lateral movement into internal networks.
• Disruption of business-critical automation.

Public scans indicate that over 100,000 n8n instances may be exposed globally.

Affected and Fixed Versions

n8n has released patched versions that properly isolate expression evaluation:

• n8n 1.120.4
• n8n 1.121.1
• n8n 1.122.0

Any deployment running an earlier version should be considered high risk.

Temporary Mitigations (Not a Replacement for Patching)

While patching is the only complete fix, risk can be reduced by:

• Restricting workflow editing permissions.
• Removing public internet exposure.
• Placing n8n behind VPNs or access gateways.
• Monitoring workflow changes and executions.

Detection Challenges

Exploitation may not be visible in standard application logs. Security teams should monitor:

• Unexpected child processes spawned by n8n.
• Abnormal command execution on the host.
• Suspicious workflow modifications.
• Anomalous outbound network connections.

Final Thought

CVE-2025-68613 demonstrates that automation engines are no longer just productivity tools — they function as execution environments embedded within organizational trust boundaries. As attackers increasingly target logic layers, defenders must apply the same security rigor to automation platforms as production systems.