Skip to main content
VulnerabilityPublished Updated

CVE-2026-72764: n8n · Resource Exposure

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium : upgrade to 1.123.67 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.8Medium
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.05.8
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.123.67, 2.32.1, 2.31.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 10 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • <1.123.67
Fixed in
  • 1.123.67
n8n-ion8nAffected
  • >=2.32.0 <2.32.1
Fixed in
  • 2.32.1
n8n-ion8nAffected
  • >=2.0.0-rc.0 <2.31.5
Fixed in
  • 2.31.5
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <1.123.67
  • <2.31.5
  • <2.32.1
Fixed in
  • 1.123.67
  • 2.31.5
  • 2.32.1
npmn8npkg:npm/n8nOther threatsAffected
  • <1.123.67
  • >=2.32.0 <2.32.1
  • >=2.0.0-rc.0 <2.31.5
Fixed in
  • 1.123.67
  • 2.32.1
  • 2.31.5

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

AI-suggested

If you cannot patch yet, operators of multi-user n8n instances running the JavaScript task runner with modules enabled should consider restricting Code-node execution permissions or isolating users to prevent cache poisoning. Monitor vendor communications for official patches or updates.

Description

n8n's JavaScript task runner shared a single module cache across all users' Code-node executions. In affected versions (before 1.123.67, 2.31.5, and 2.32.1), a user able to run a Code node could poison a cached module and thereby alter other users' Code-node executions on the same runner, affecting their confidentiality, integrity, or availability. This is a cross-user isolation break within a single n8n instance and does not constitute a sandbox escape or remote code execution. Only multi-user instances running the JS task runner with built-in or external modules enabled are affected.

References

Community reviews

Loading reviews…