目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2026-27493— n8n 安全漏洞

一分钟漏洞结论

影响对象
n8n-io n8n
利用判断
尚无明确在野利用证据,仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本;无法立即升级时,限制受影响服务暴露并加强监测。

n8n是n8n开源的一个可扩展的工作流自动化工具。 n8n 2.10.1之前版本、2.9.3之前版本和1.123.22之前版本存在安全漏洞,该漏洞源于Form节点存在二阶表达式注入,可能导致未经验证的攻击者通过提交特制表单数据注入并执行任意n8n表达式。

AI 预测 7.5 利用难度: 困难 EPSS 1.57% · P75
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2026-27493 基础信息

漏洞信息

对漏洞内容有疑问?看看神龙的深度分析是否有帮助!
查看神龙十问 ↗

尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。

Vulnerability Title
n8n has Unauthenticated Expression Evaluation via Form Node
来源: CVE Program / CVE List V5
Vulnerability Description
n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, a second-order expression injection vulnerability existed in n8n's Form nodes that could allow an unauthenticated attacker to inject and evaluate arbitrary n8n expressions by submitting crafted form data. When chained with an expression sandbox escape, this could escalate to remote code execution on the n8n host. The vulnerability requires a specific workflow configuration to be exploitable. First, a form node with a field interpolating a value provided by an unauthenticated user, e.g. a form submitted value. Second, the field value must begin with an `=` character, which caused n8n to treat it as an expression and triggered a double-evaluation of the field content. There is no practical reason for a workflow designer to prefix a field with `=` intentionally — the character is not rendered in the output, so the result would not match the designer's expectations. If added accidentally, it would be noticeable and very unlikely to persist. An unauthenticated attacker would need to either know about this specific circumstance on a target instance or discover a matching form by chance. Even when the preconditions are met, the expression injection alone is limited to data accessible within the n8n expression context. Escalation to remote code execution requires chaining with a separate sandbox escape vulnerability. The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations. Review usage of form nodes manually for above mentioned preconditions, disable the Form node by adding `n8n-nodes-base.form` to the `NODES_EXCLUDE` environment variable, and/or disable the Form Trigger node by adding `n8n-nodes-base.formTrigger` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
来源: CVE Program / CVE List V5
Vulnerability Type
对生成代码的控制不恰当(代码注入)
来源: CVE Program / CVE List V5
Vulnerability Title
n8n 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
n8n是n8n开源的一个可扩展的工作流自动化工具。 n8n 2.10.1之前版本、2.9.3之前版本和1.123.22之前版本存在安全漏洞,该漏洞源于Form节点存在二阶表达式注入,可能导致未经验证的攻击者通过提交特制表单数据注入并执行任意n8n表达式。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
n8n-io n8n < 1.123.22 -

二、漏洞 CVE-2026-27493 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-27493 的情报信息

请登录查看更多情报信息。

CVE-2026-27493 补丁与修复 (1)

同批安全公告 · n8n-io · 2026-02-25 · 共 7 条

CVE-2026-27577 9.4 CRITICAL n8n 代码注入漏洞
CVE-2026-27495 n8n 代码注入漏洞
CVE-2026-27494 n8n 安全漏洞
CVE-2026-27497 n8n 代码注入漏洞
CVE-2026-27578 n8n 安全漏洞
CVE-2026-27498 n8n 代码注入漏洞

IV. Related Vulnerabilities

V. Comments for CVE-2026-27493

暂无评论


发表评论