CVE-2026-86077
mediumpriority · track · 26OT risk · elevatedEPSS 0.004 · 37 %ileDEUSEPSS · scored 2026-10-27
n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the /chat WebSocket route accepted a resumeToken and resumed a paused execution without checking that the target node supported chat messages. An anonymous form submitter who received that token could reuse it on the chat route to release a Send-and-Wait, non-chat HITL, or Wait approval gate. The affected authorization logic is packages/cli/src/chat/chat-execution-manager.ts, where canResumeOverChat did not gate the resume target. This issue is fixed in versions 2.37.7 and 2.38.2.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.7–6.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (10)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-3165n8n: Mehrere SchwachstellenDeutsch2026-09-02csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in n8n ausnutzen, um Sicherheitsmechanismen zu umgehen, beliebigen Code auszuführen oder einen Denial of Service zu verursachen.
- GHSA-35jj-42hp-8gmqn8n: Anonymous Approval-Gate Bypass via Reused resumeToken over the Chat WebSocket2026-09-10ghsa · osvUS
## Impact The `/chat` WebSocket route resumed a paused execution from a resume token without checking that the node being resumed was a chat node. n8n hands that token to anonymous form submitters, so a party with no account could present it on the chat route and release an execution waiting at an approval gate, the control an author puts in front of an action considered too consequential to automate. The patch restricts resume over the chat route and Chat Hub to chat-capable node types. ## Patches The issue has been fixed in n8n versions 2.37.7 and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Avoid workflows that combine a Form Trigger with non-chat approval gates (Send-and-Wait, Telegram/Slack/Gmail HITL, or plain Wait nodes) on publicly accessible instances. - Audit recent executions of such workflows for unexpected completion without a corresponding approval callback. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
sources
Which sources assert this record, and when.
references (3) nvd
External citations — patches, advisories, analysis.
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7Release Notes
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2Release Notes
- https://github.com/n8n-io/n8n/security/advisories/GHSA-35jj-42hp-8gmqMitigationVendor Advisory
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan