Workflow data injection via missing webhook verification
Published Jul 8, 2026 · Updated Jul 8, 2026
Authentication bypass in n8n 1.x before 1.123.18 and 2.0.0 through 2.6.1 allows remote attackers to inject forged Zendesk webhook data. The ZendeskTrigger node accepts POST bodies without computing and verifying the HMAC-SHA256 signature attached by Zendesk. Exploitation requires an active Zendesk-triggered workflow and knowledge of its high-entropy webhook URL, after which crafted data can drive downstream workflow actions.
Summary
What happened
Authentication bypass in n8n 1.x before 1.123.18 and 2.0.0 through 2.6.1 allows remote attackers to inject forged Zendesk webhook data. The ZendeskTrigger node accepts POST bodies without computing and verifying the HMAC-SHA256 signature attached by Zendesk. Exploitation requires an active Zendesk-triggered workflow and knowledge of its high-entropy webhook URL, after which crafted data can drive downstream workflow actions.
The record
- CVE
- CVE-2026-56360
- Published
- Jul 8, 2026
- Updated
- Jul 8, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-290, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2026CVE publishedPublication date reported by the CVE source.
- Jul 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.123.18
- Affected versionversion=2.0.0 <2.6.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo