dbcve.org
N8nApplication

CVE-2026-42228

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 1.123.32 / 2.17.4 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, the /chat WebSocket endpoint used by the Chat Trigger node's Hosted Chat feature did not verify that an incoming connection was authorized to interact with the target execution. An unauthenticated remote attacker who could identify a valid execution ID for a workflow in a waiting state could attach to that execution, receive the pending prompt intended for the legitimate user, and submit arbitrary input to resume or influence downstream workflow behavior. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.

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 · high confidence

The /chat WebSocket endpoint in n8n's Chat Trigger node failed to verify that incoming connections were authorized to interact with target workflow executions. An unauthenticated attacker who could guess valid execution IDs for workflows in a waiting state could attach to those executions, intercept the pending prompt, and submit arbitrary input to influence workflow behavior.

MitigationUpgrade to n8n versions 1.123.32, 2.17.4, or 2.18.1 which contain the authorization verification patch for the WebSocket endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 1.123.32>= 2.17.0, < 2.17.4= 2.18.0

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
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

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 'n8n --version' from command line, or check the version in the UI under Settings > About, or inspect the package.json file in the n8n installation directory
    Affected if Version is < 1.123.32 OR (>= 2.17.0 AND < 2.17.4) OR = 2.18.0
  2. Locate workflows using Chat Trigger node
    In n8n UI, search for workflows containing the 'Chat Trigger' node, or query the workflow database/JSON files for nodes of type 'n8n-nodes-base.chatTrigger'
    Affected if Any active workflow uses the Chat Trigger node and is in a waiting state or can receive chat input
  3. Verify WebSocket endpoint exposure
    Check if the /chat WebSocket endpoint is accessible from untrusted networks. Inspect n8n server configuration, proxy settings, and firewall rules. Attempt a WebSocket connection to wss://<your-n8n-host>/chat from an unauthorized client
    Affected if The /chat WebSocket endpoint accepts connections without additional authentication beyond n8n's basic auth
  4. Check for workflow executions in waiting state
    In n8n UI, go to Executions view and filter for executions with status 'Waiting' or 'Paused', or query the execution database for executions where status indicates a waiting state
    Affected if There are executions in a waiting state with predictable or enumerable execution IDs
  5. Inspect WebSocket authentication configuration
    Review n8n configuration files (config.yaml, environment variables) for WebSocket authentication settings. Check if WebSocket security options are enabled under Settings > Security > Webhooks & APIs
    Affected if WebSocket authentication for the /chat endpoint is not explicitly enforced or configured

You are affected if your n8n version falls within the vulnerable ranges AND you have active workflows using the Chat Trigger node with accessible /chat WebSocket endpoint and potentially exposed waiting executions.

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
Upgrade available Upgrade to 1.123.32 / 2.17.4 or later
Fixed in 1.123.322.17.4
Interim mitigation

Upgrade to n8n versions 1.123.32, 2.17.4, or 2.18.1 which contain the authorization verification patch for the WebSocket endpoint.

Recommended fix High confidence

1.123.32 for 1.x users; 2.17.4 for 2.17.x users; 2.18.1 for 2.18.x users

  1. Identify which n8n major version line you are currently running (1.x or 2.x)
  2. If running 1.x version: upgrade to n8n version 1.123.32 or later
  3. If running 2.17.x version: upgrade to n8n version 2.17.4 or later
  4. If running 2.18.0: upgrade to n8n version 2.18.1
  5. After upgrading, verify the Chat Trigger node's Hosted Chat functionality works correctly with the security fix applied

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

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42228 — 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-42228 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