n8n 1.121.0 for Node.js
Approved changes feed: RSS · Atom
cpe:2.3:a:n8n:n8n:1.121.0:*:*:*:*:node.js:*:*
part: a version: 1.121.0 update: *
| Vendor | N8N (520b99b7-b772-5ae7-8c78-fc4545db5e77) |
|---|---|
| Product | N8N (5119654b-d981-5551-be49-635f90cc3028) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/n8n-io/n8n |
purl2cpe | 2026-06-01 10:14:08.240056 |
pkg:golang/github.com/n8n-io/n8n |
purl2cpe | 2026-06-01 10:14:08.240058 |
pkg:npm/n8n |
purl2cpe | 2026-06-01 10:14:08.240059 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-68613 |
vulnerable | 2026-06-08 07:41:21.452206 |
n8n Vulnerable to Remote Code Execution via Expression Injection
CRITICAL (10)
n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.
Published: 2025-12-19T22:23:47.777Z
Updated: 2026-03-12T03:55:15.270Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.