CVE-2025-68613criticalbajo ataqueCWE-913

CVE-2025-68613: fallo crítico en n8n-io n8n

n8n Vulnerable to Remote Code Execution via Expression Injection

Publicada el · Actualizada el

Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.

100Vexday Risk Score

Corrige ahora. Ella está bajo explotación confirmada por CISA y tiene exploit funcional público.

ssvc Actcvss 10epss 99%
de la publicación al arma3 días
Publicada en NVD19 dic
1ª PoC+3d
metasploit10 jun
CISA KEV+82d
Acción exigida por CISAplazo federal: 2026-03-25

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

En resumen

La plataforma de automatización de flujos de trabajo n8n tiene una falla crítica que permite a usuarios autenticados ejecutar código malicioso en el servidor al inyectar expresiones dañinas en los flujos de trabajo. Esto podría otorgar a los atacantes control total del sistema y acceso a todos los datos que almacena.

Detalle técnico

Vulnerabilidad de Ejecución Remota de Código en el sistema de evaluación de expresiones de n8n (versiones 0.211.0 a 1.120.3, 1.121.0, 1.122.0-beta) permite que atacantes autenticados escapen del sandbox de expresiones y ejecuten código arbitrario con privilegios del proceso n8n a través de contextos de expresión de flujo de trabajo insuficientemente aislados. La explotación requiere acceso a la configuración de flujos de trabajo y resulta en compromiso total de la instancia, incluida exfiltración de datos y ejecución de comandos a nivel del sistema operativo.

Resumen generado y traducido por IA a partir de la descripción oficial.

El análisis completo de esta CVE está disponible en portugués →

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Productos afectados
n8n-io · n8n
PoCs públicas encontradas — 50
githubgithub.com/wioui/n8n-CVE-2025-68613-exploit★ 98githubgithub.com/rxerium/CVE-2025-68613★ 28githubgithub.com/TheStingR/CVE-2025-68613-POC★ 25githubgithub.com/LingerANR/n8n-CVE-2025-68613★ 7githubgithub.com/hackersatyamrastogi/n8n-exploit-CVE-2025-68613-n8n-God-Mode-Ultimate★ 5githubgithub.com/Ak-cybe/CVE-2025-68613-n8n-rce-analysis★ 1githubgithub.com/JohannesLks/CVE-2025-68613-Python-Exploit★ 1githubgithub.com/mbanyamer/n8n-Authenticated-Expression-Injection-RCE-CVE-2025-68613★ 1githubgithub.com/releaseown/analysis-and-poc-n8n-CVE-2025-68613★ 1githubgithub.com/Khin-96/n8n-cve-2025-68613-thm★ 1githubgithub.com/AbdulRKB/n8n-RCE★ 0githubgithub.com/Dlanang/homelab-CVE-2025-68613★ 0githubgithub.com/J4ck3LSyN-Gen2/n8n-CVE-2025-68613-TryHackMe★ 0githubgithub.com/gagaltotal/n8n-cve-2025-68613★ 0githubgithub.com/cv-sai-kamesh/n8n-CVE-2025-68613★ 0githubgithub.com/Rishi-kaul/n8n-CVE-2025-68613★ 0githubgithub.com/ahmedshamsddin/n8n-RCE-CVE-2025-68613★ 0githubgithub.com/TheInterception/n8n_CVE-2025-68613_exploit_payloads★ 0githubgithub.com/Victorhugofariasvieir66/relatorio-n8n.md★ 0githubgithub.com/h3raklez/CVE-2025-68613★ 0githubgithub.com/canpilayda/n8n-RCE-CVE-2025-68613★ 0githubgithub.com/azilRababe/CVE-2025-68613★ 0githubgithub.com/manyaigdtuw/CVE-2025-68613_Scanner★ 0githubgithub.com/sahilccras/Blackash-CVE-2025-68613★ 0githubgithub.com/reem-012/poc_CVE-2025-68613★ 0githubgithub.com/intbjw/CVE-2025-68613-poc-via-copilot★ 0githubgithub.com/ali-py3/Exploit-CVE-2025-68613★ 0githubgithub.com/nehkark/CVE-2025-68613★ 0githubgithub.com/GnuTLam/POC-CVE-2025-68613★ 0githubgithub.com/secjoker/CVE-2025-68613★ 0githubgithub.com/r4j3sh-com/CVE-2025-68613-n8n-lab★ 0githubgithub.com/intelligent-ears/CVE-2025-68613★ 0vulncheckvulncheck.com/xdb/ab094f27628bno verificadovulncheckvulncheck.com/xdb/82f9d593ab6eno verificadovulncheckvulncheck.com/xdb/86b2b24fbfa7no verificadovulncheckvulncheck.com/xdb/3f9ad21a5118no verificadovulncheckvulncheck.com/xdb/fcdba2f77fdbno verificadovulncheckvulncheck.com/xdb/d1743afcb925no verificadovulncheckvulncheck.com/xdb/5fac5c175f22no verificadovulncheckvulncheck.com/xdb/aac8c4008646no verificadovulncheckvulncheck.com/xdb/a0411d24fed5no verificadovulncheckvulncheck.com/xdb/bd6e0d307ee2no verificadovulncheckvulncheck.com/xdb/9687217c6c33no verificadovulncheckvulncheck.com/xdb/fead37a6986dno verificadovulncheckvulncheck.com/xdb/9f63a4ae5759no verificadovulncheckvulncheck.com/xdb/4e2719893e8fno verificadovulncheckvulncheck.com/xdb/c314ba54ddaano verificadovulncheckvulncheck.com/xdb/4d6a79132e16no verificadovulncheckvulncheck.com/xdb/f38b6c93c18eno verificadovulncheckvulncheck.com/xdb/54ee0cc1d1b3no verificado
⚠ Recursos públicos, para evaluar la exposición de sistemas que controlas o estás autorizado a probar. Prueba solo con autorización.