Guardrail instruction bypass via crafted end-user input
Published Jul 15, 2026 · Updated Jul 15, 2026
Improper input validation in the Guardrail node in n8n before 2.10.0 allows remote attackers to bypass configured workflow safeguards. The node accepts crafted end-user text that circumvents its default guardrail instructions; n8n has not disclosed the specific parsing or validation error. Exploitation requires a reachable workflow that uses the Guardrail node, and the demonstrated consequence is reduced workflow integrity rather than data disclosure or service interruption.
Summary
What happened
Improper input validation in the Guardrail node in n8n before 2.10.0 allows remote attackers to bypass configured workflow safeguards. The node accepts crafted end-user text that circumvents its default guardrail instructions; n8n has not disclosed the specific parsing or validation error. Exploitation requires a reachable workflow that uses the Guardrail node, and the demonstrated consequence is reduced workflow integrity rather than data disclosure or service interruption.
The record
- CVE
- CVE-2026-56349
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 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 <2.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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