Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-68613: n8n Vulnerable to Remote Code Execution via Expression Injection

Noroxi assessment

Priority: Now (action score 95/100)

  • CISA has confirmed exploitation in the wild (Mar 11, 2026). Remediation deadline for US federal agencies: Mar 25, 2026.
  • A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 98.9% (FIRST EPSS); higher than 99.9% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: n8n (npm) 1.120.4, 1.121.1.

Patch today or shut off access. Upgrade to n8n (npm) 1.120.4, 1.121.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

HighCVSS 8.8 · v3.1KEVWeaponized Fix available
Published
Dec 19, 2025
Updated
Oct 13, 2026
EPSS
98.9% · 99th percentile

Report tools

JSON

Action score

95

Now

Patch today or shut off access.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
30 / 30 · Listed
EPSS
30 / 30 · 98.9%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitHub_M
9.9
1.1 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Mar 11, 2026. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Mar 25, 2026.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68613

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for n8n records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
n8nn8n

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • n8n n8n0.211.0 and later · before 1.120.4
  • n8n n8n1.121.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • n8n-io n8n

    • >= 0.211.0, < 1.120.4, = 1.121.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmn8nfrom 0.211.0 · before 1.120.41.120.4
npmn8nfrom 1.121.0 · before 1.121.11.121.1

Same product

n8n: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
    63This week
  • CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
    45Plan
  • CVE-2025-68668n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node
    43Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-62726Oct 30, 2025 · n8n Vulnerable to Remote Code Execution via Git Node Pre-Commit Hook
    35Monitor
  • ← EarlierCVE-2025-65964Dec 9, 2025 · n8n Vulnerable to Remote Code Execution via Git Node Custom Pre-Commit Hook
    37Monitor
  • Later →CVE-2025-61914Dec 26, 2025 · n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:n8n1.120.4Package registry (OSV)
npm:n8n1.121.1Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×37

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2025-68613 —
Metasploit moduleexploit/multi/http/n8n_workflow_expression_rcen8n Workflow Expression Remote Code Executionexploit2025-06-10
Proof-of-concept repository on GitHubstars:12025-12-26
Proof-of-concept repository on GitHubstars:272025-12-22
Proof-of-concept repository on GitHubstars:292025-12-22
Proof-of-concept repository on GitHubstars:02025-12-22
Proof-of-concept repository on GitHubstars:1052025-12-22
Proof-of-concept repository on GitHubstars:02025-12-23
Proof-of-concept repository on GitHubstars:02025-12-23
Proof-of-concept repository on GitHubstars:02025-12-23
Proof-of-concept repository on GitHubstars:02025-12-23
Proof-of-concept repository on GitHubstars:02025-12-23

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-193 d
  2. Published
  3. First PoC+2 d
  4. CISA KEV+81 d
  5. TodayOct 26, 2026+311 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-2504947 days apartn8n Has an Expression Escape Vulnerability Leading to RCE
    37Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-913 · Improper Control of Dynamically-Managed Code Resources

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records