| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.38+ |
Summary
A vulnerability, which was classified as critical, has been found in n8n up to 1.123.21/2.9.2/2.10.0. Impacted is an unknown function of the component Chat Trigger. This manipulation causes config. The identification of this vulnerability is CVE-2026-56353. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability has been found in n8n up to 1.123.21/2.9.2/2.10.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the component Chat Trigger. The manipulation with an unknown input leads to a config vulnerability. The CWE definition for the vulnerability is CWE-16. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
n8n contains an authentication bypass in the Chat Trigger node when configured with n8n User Auth (a non-default configuration). In affected releases — before 1.123.22, the 2.0.0 through 2.9.2 line, and 2.10.0 — the authentication check on the Chat Trigger webhook endpoint can be circumvented, allowing access without valid credentials. Fixed in 1.123.22, 2.9.3, and 2.10.1.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-56353 since 06/20/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592.004 according to MITRE ATT&CK.
Upgrading to version 1.123.22, 2.9.3 or 2.10.1 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 1.123.0
- 1.123.1
- 1.123.2
- 1.123.3
- 1.123.4
- 1.123.5
- 1.123.6
- 1.123.7
- 1.123.8
- 1.123.9
- 1.123.10
- 1.123.11
- 1.123.12
- 1.123.13
- 1.123.14
- 1.123.15
- 1.123.16
- 1.123.17
- 1.123.18
- 1.123.19
- 1.123.20
- 1.123.21
- 2.0
- 2.1
- 2.2
- 2.3
- 2.4
- 2.5
- 2.6
- 2.7
- 2.8
- 2.9
- 2.9.0
- 2.9.1
- 2.9.2
- 2.10.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: ConfigCWE: CWE-16
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: n8n 1.123.22/2.9.3/2.10.1
Timeline
06/20/2026 CVE reserved07/15/2026 Advisory disclosed
07/15/2026 VulDB entry created
07/15/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-56353 (🔒)
GCVE (CVE): GCVE-0-2026-56353
GCVE (VulDB): GCVE-100-379219
Entry
Created: 07/15/2026 14:20Changes: 07/15/2026 14:20 (18), 07/15/2026 14:21 (34)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.