dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-56349

MEDIUM · 6.3 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
n8n before version 2.10.0 contains an input validation vulnerability in the Guardrail node that allows attackers to bypass default guardrail instructions. End users can craft malicious inputs to circumvent guardrail protections and compromise workflow integrity.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

n8n before version 2.10.0 contains an input validation vulnerability in the Guardrail node. Attackers can craft malicious inputs that bypass default guardrail instructions, allowing circumvention of protective controls and compromising workflow integrity.

MitigationUpgrade to n8n version 2.10.0 or later to patch the input validation vulnerability in the Guardrail node. Review existing workflows using Guardrail nodes for any evidence of attempted or successful bypasses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed n8n version
    Run the command 'n8n --version' or check the version via the UI under Settings > About. Alternatively, inspect the package.json file in the n8n installation directory for the 'version' field.
    Affected if The installed version is lower than 2.10.0 (e.g., 2.9.x, 2.8.x, etc.)
  2. Locate Guardrail nodes in workflows
    Export all workflows and search for nodes with type 'n8n-nodes-base.guardrail' or visually inspect workflows in the UI for any Guardrail node instances.
    Affected if Any workflow contains one or more Guardrail nodes and the n8n version is below 2.10.0
  3. Inspect Guardrail node configuration
    Open each Guardrail node in the workflow editor and review the Instructions and Rules fields. Check if default guardrail instructions are present or if custom validation rules are configured.
    Affected if Guardrail nodes are present with default or custom instructions, and the n8n version is vulnerable (below 2.10.0)
  4. Review workflow execution logs
    Access the execution history for workflows containing Guardrail nodes. Look for any unusual or unexpected execution patterns that may indicate a bypass attempt.
    Affected if Execution logs show unexpected behavior or successful bypasses, combined with a vulnerable version in use

You are affected if your n8n installation version is before 2.10.0 and you have workflows using the Guardrail node, as the input validation flaw allows malicious inputs to bypass guardrail instructions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to n8n version 2.10.0 or later to patch the input validation vulnerability in the Guardrail node. Review existing workflows using Guardrail nodes for any evidence of attempted or successful bypasses.

Recommended fix Moderate confidence

n8n version 2.10.0 or later

  1. 1. Identify the current n8n version in use (e.g., check the UI footer, Docker tag, or package.json)
  2. 2. If running a version before 2.10.0, plan the upgrade to version 2.10.0 or later
  3. 3. For Docker deployments: Update the image tag to 'n8n:latest' or specifically 'n8n:2.10.0' or newer
  4. 4. For npm installations: Run 'npm install -g n8n@latest' or 'npm install -g [email protected]'
  5. 5. For self-hosted installations: Update via your package manager or follow the official upgrade documentation
  6. 6. After upgrading, verify the Guardrail node functionality to confirm the vulnerability is resolved
  7. 7. Review any custom guardrail configurations to ensure they were not previously compromised

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56349 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data