NPM · MAY 2026 · EARLY WARNING

n8n npm Package Vulnerability: XML Node Patch Bypass Under Investigation

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

GHSA-WRWR-H859-XH2RGHSA-HQR4-H3XV-9M3RSeverity: HIGH

An authenticated user with permission to create or modify workflows in the n8n npm package could reportedly bypass a critical patch, potentially leading to remote code execution on the n8n host.

What happened

The n8n npm package is under investigation for a potential vulnerability tracked as GHSA-WRWR-H859-XH2R and GHSA-HQR4-H3XV-9M3R. An authenticated user with permission to create or modify workflows could bypass the patch for GHSA-hqr4-h3xv-9m3r in the XML node. When combined with other nodes, this could lead to remote code execution (RCE) on the n8n host.

Affected versions include n8n (npm) <1.123.43, <2.20.7, or <2.22.1. It is recommended to upgrade to n8n versions 1.123.43, 2.20.7, or 2.22.1 or later to remediate the vulnerability. Users should consult the primary sources for more detailed information and to confirm the status of this potential threat.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If n8n is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats