Threats / n8n / CVE-2025-68613
CVE-2025-68613
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
n8n vulnerability
n8n contains an improper control of dynamically managed code resources vulnerability in workflow expression evaluation that enables remote code execution.
Verdict
Today item — known-exploited.
An attacker can execute arbitrary code on n8n instances by exploiting insufficient controls over dynamically evaluated expressions in workflows. This vulnerability is actively exploited in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-11).
Probability (EPSS)
EPSS 0.98011 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: n8n, n8n. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-913 Improper Control of Dynamic Code.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious workflow or inject a payload into an existing workflow expression field that n8n will dynamically evaluate.
Business
Attackers gain code execution within the n8n runtime environment, compromising confidentiality, integrity, and availability of automation infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands or scripts within the context of the n8n process, potentially accessing sensitive data, credentials, or connected systems.
Business
Downstream systems and data sources connected to n8n become accessible to the attacker, enabling lateral movement and data exfiltration.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence or pivot to other infrastructure by leveraging the compromised n8n instance as a foothold.
Business
The organization faces extended dwell time, expanded breach scope, and difficulty in incident containment and recovery.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05