n8n-io n8n up to 1.123.16/2.5.1 Expressions dynamically-managed code resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.89 |
Summary
A vulnerability identified as critical has been detected in n8n-io n8n up to 1.123.16/2.5.1. Affected by this issue is some unknown functionality of the component Expressions Handler. Performing a manipulation results in dynamically-managed code resources. This vulnerability is reported as CVE-2026-25049. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in n8n-io n8n up to 1.123.16/2.5.1. This affects some unknown functionality of the component Expressions Handler. The manipulation with an unknown input leads to a dynamically-managed code resources vulnerability. CWE is classifying the issue as CWE-913. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
n8n is an open source workflow automation platform. Prior to versions 1.123.17 and 2.5.2, an authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. This issue has been patched in versions 1.123.17 and 2.5.2.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-25049 since 01/28/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 298984 (n8n Node.js Package < 1.123.17 / 2.x < 2.5.2 Expression Escape Leading to RCE (CVE-2026-25049)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.123.17 or 2.5.2 eliminates this vulnerability. Applying the patch 7860896909b3d42993a36297f053d2b0e633235d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (298984) and CERT Bund (WID-SEC-2026-0318). Be aware that VulDB is the high quality source for vulnerability data.
Affected
- n8n n8n
Product
Vendor
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
- 2.5.0
- 2.5.1
License
Website
- Product: https://github.com/n8n-io/n8n/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.9
NVD Vector: 🔒
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: Dynamically-managed code resourcesCWE: CWE-913
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 298984
Nessus Name: n8n Node.js Package < 1.123.17 / 2.x < 2.5.2 Expression Escape Leading to RCE (CVE-2026-25049)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: n8n 1.123.17/2.5.2
Patch: 7860896909b3d42993a36297f053d2b0e633235d
Timeline
01/28/2026 CVE reserved02/04/2026 Advisory disclosed
02/04/2026 VulDB entry created
02/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6cqr-8cfr-67f8
Status: Confirmed
CVE: CVE-2026-25049 (🔒)
GCVE (CVE): GCVE-0-2026-25049
GCVE (VulDB): GCVE-100-344367
CERT Bund: WID-SEC-2026-0318 - n8n: Mehrere Schwachstellen
Entry
Created: 02/04/2026 18:35Updated: 02/14/2026 05:13
Changes: 02/04/2026 18:35 (69), 02/05/2026 16:14 (7), 02/06/2026 05:28 (11), 02/14/2026 05:13 (2)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.