VulnerabilityPublished 24 Jun 2026Updated 29 Oct 2026

CVE-2026-56358: n8n · Cross-site Scripting

Affects n8nSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.11.2 or 1.123.25 when convenient.

Data as of 29 Oct 2026, 18:49 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	5.1
CNA (VulnCheck)	CVSS 3.1	5.4

EPSS

0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-24.

Patch

Available – fixed in 2.11.2, 1.123.25

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade n8n to 2.11.2 or 1.123.25; n8n to 2.11.2; n8n to 1.123.25.

Affected software

Product	Affected	Fixed in
n8nn8n	Affected >=2.0.0-rc.0 <2.11.2	Fixed in 2.11.2
n8nn8n	Affected <1.123.25	Fixed in 1.123.25
n8nn8n	Affected >=2.0.0-rc.0 <2.11.2	Fixed in 2.11.2
n8nn8n	Affected <1.123.25	Fixed in 1.123.25
npmn8n`pkg:npm/n8n`Other threats	Affected <1.123.25 >=2.0.0-rc.0 <2.11.2	Fixed in 1.123.25 2.11.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official fixes by upgrading n8n to version 1.123.25 or later in the 1.x branch, or to version 2.11.2 or later in the 2.x branch. No other mitigations are indicated or necessary once patched.

Description

CVE-2026-56358 is a stored cross-site scripting (XSS) vulnerability in n8n affecting versions before 1.123.25 (1.x) and before 2.11.2 (2.x). The flaw exists in the Form Trigger node's CSS sanitization, allowing authenticated users with workflow creation permissions to inject malicious scripts. These scripts execute persistently for all visitors of the affected forms, potentially enabling form hijacking and phishing attacks. The vulnerability has a medium severity with a CVSS 4.0 score of 5.1. Fixes are available in versions 1.123.25 and 2.11.2 and later.

Impact

An attacker with workflow creation permissions can inject persistent XSS payloads in the Form Trigger node, which execute in the browsers of form visitors. This can lead to form hijacking and phishing attacks, compromising user trust and potentially exposing sensitive information. The vulnerability requires authenticated access with specific permissions and does not allow privilege escalation or direct system compromise.

Summary

n8n versions prior to 1.123.25 (1.x) and 2.11.2 (2.x) contain a stored cross-site scripting vulnerability in the Form Trigger node's CSS sanitization process. Authenticated users who can create workflows may inject malicious JavaScript payloads that persistently execute when other users visit the affected forms. This vulnerability can be exploited to hijack forms and conduct phishing attacks. The issue is addressed in n8n versions 1.123.25 and 2.11.2, with the fix also included in 2.12.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 18:49 UTC

Technical details

References

Community reviews

Related threats