CVE-2025-68613 is an improper control of dynamically-managed code resources vulnerability in n8n n8n. CISA added it to the Known Exploited Vulnerabilities catalogue on 11 March 2026, which means attackers have used it in real attacks. n8n contains an improper control of dynamically managed code resources vulnerability in its workflow expression evaluation system that allows for remote code execution.
What the vulnerability is in n8n
This CVE sits in n8n’s workflow expression evaluation path, where user-controlled expressions can be processed as code-like input. That matters because dynamically managed code resources are a common place for trust boundaries to break, especially when the platform is expected to interpret workflow content safely rather than execute attacker-influenced logic.
In practice, the risk is not just that a malformed expression fails, but that the expression engine can be abused to cross from data handling into code execution. For workflow automation platforms, that usually means the blast radius can extend beyond one workflow to the broader runtime environment if the platform is over-privileged or exposed to untrusted input.
Why this kind of flaw is dangerous
Improper control of dynamically managed code resources is dangerous because the product is taking untrusted, variable, or runtime-generated content and treating it with more authority than it deserves. In an automation platform, that can turn ordinary workflow features into an execution primitive, which is why remote code execution is such a severe outcome.
Even when the initial entry point looks like “just an expression,” the downstream consequence can include command execution, data access, secret access, lateral movement, or persistence. If the platform stores credentials, tokens, or integration secrets, an RCE foothold can quickly become broader environment compromise.
How organisations should assess exposure
Exposure checks should start with a precise inventory of where n8n is deployed, how it is exposed, and whether untrusted users, tenants, or integrations can influence workflow expressions. The official CVE Program and NIST National Vulnerability Database should be used for authoritative record details, while vendor advisories should be used for exact version and fix guidance.
Security teams should also review whether the service is internet-facing, whether it is reachable from shared internal networks, and whether workflow authors can import or edit expressions from less trusted sources. A platform that is isolated and tightly governed has a much smaller practical attack surface than one that is broadly exposed.
Remediation, detection, and post-patch review
The preferred response is to remove the vulnerable version or apply the vendor’s fix as soon as it is available, but remediation should also include compensating controls where patching is delayed. Restrict who can create or edit workflows, reduce runtime privilege, limit outbound network access from the n8n host, and treat expression evaluation as a high-risk execution boundary.
Detection should focus on signs of unexpected process creation, unusual outbound connections, new files, or abnormal workflow behaviour around the time of exploitation. After patching, review the host for persistence, injected workflow content, altered credentials, and any evidence that the application runtime or connected integrations were abused after initial compromise.
Risk and Threat Considerations
This vulnerability is attractive to attackers because workflow platforms often sit close to business logic, integrations, and credentials. If an attacker can turn expression processing into code execution, they may pivot from a single application flaw into broader access across connected systems.
Failure mechanism: Untrusted workflow content is evaluated with excessive authority, allowing code execution instead of safe interpretation.
Impact: Attackers can steal secrets, alter automations, move laterally, or persist inside the automation environment and any connected services.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | n8n exposure depends on hardened deployment and restricted runtime settings. |
| Recommendation — Harden n8n deployment settings and remove unnecessary exposure paths. | ||
| NIST SP 800-53 Rev 5 | SI-10 — Information Input Validation | The flaw centers on unsafe handling of expression input treated like code. |
| SI-16 — Memory Protection | RCE outcomes require runtime safeguards against unsafe execution behavior. | |
| Recommendation — Validate and constrain workflow expression input before execution. Limit unsafe execution paths and enforce runtime isolation controls. | ||
| NIST CSF 2.0 | PR.PS-01 — Platform Security | Secure platform configuration and hardening directly reduce exploitability. |
| Recommendation — Harden the automation platform and restrict high-risk execution features. | ||
| MITRE ATT&CK | T1059 — Command and Scripting Interpreter | Remote code execution commonly maps to attacker execution through interpreters. |
| Recommendation — Detect interpreter abuse and unexpected script execution on the host. | ||
Practitioner Guidance
Why practitioners should care: This is not just an application bug, it is a platform trust failure with potential reach into the systems n8n automates. When automation engines can execute attacker-influenced logic, the operational impact can be much larger than the initial web-facing entry point.
What to watch for: Pay close attention to any deployment where workflow authors are numerous, integrations are sensitive, or the platform runs with broad cloud, network, or secret access. Those conditions increase the likelihood that exploitation becomes a full environment incident rather than a contained application issue.
Practitioner takeaway: Treat workflow expression handling as a privileged execution surface, not a convenience feature.
Related resources from NHI Mgmt Group
- How do IAM and NHI controls change when CDN resources become code-managed?
- What breaks when Transit Gateway resources are managed manually instead of as code?
- Who is accountable for Terraform governance when some code is managed and some code is still outside control?
- Why does public exploit code make CVE-2025-31324 more dangerous?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org