n8n before 1.123.67 Module Cache Poisoning via Code Node (CVE-2026-72764) | HOL Guard CVE

Medium · CVSS 5.8CVE-2026-72764GHSA-9CMH-XCQM-5HQR

n8n before 1.123.67 Module Cache Poisoning via Code Node

Answer in brief

CVE-2026-72764 records a Medium severity (CVSS 5.8) vulnerability in n8n before 1.123.67 Module Cache Poisoning via Code Node. The current sources do not mark it as known exploited. The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic), n8n-io/n8n (generic), n8n (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 11, 2026Updated Sep 18, 2026Source checked Sep 25, 2026First seen by HOL Aug 11, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.8
Exploitation: Not marked as known exploited
Affected software: 8 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 5.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic), n8n-io/n8n (generic), n8n (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:n8n:n8n:2.32.0:::::node.js::	Not reported	Not reported
cpe:2.3:a:n8n:n8n::::::node.js::*	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
n8n-io/n8ngeneric	>=0 <1.123.67	1.123.67
n8n-io/n8ngeneric	>=0 <2.32.1	2.32.1
n8n-io/n8ngeneric	>=0 <2.31.5	2.31.5
n8nnpm	>=0 <1.123.67	1.123.67
n8nnpm	>=2.32.0 <2.32.1	2.32.1
n8nnpm	>=2.0.0-rc.0 <2.31.5	2.31.5

Recommended response

Check inventory. Check lockfiles and deployed manifests for n8n-io/n8n, n8n-io/n8n, n8n-io/n8n.
Review the reported fix. Update n8n-io/n8n to 1.123.67; n8n-io/n8n to 2.32.1; n8n-io/n8n to 2.31.5; n8n to 1.123.67; n8n to 2.32.1; n8n to 2.31.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 11, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.