How severe is GHSA-hv53-3329-vmrm?

No CVSS score has been assigned to GHSA-hv53-3329-vmrm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hv53-3329-vmrm?

GHSA-hv53-3329-vmrm affects the following packages: n8n (npm), n8n (npm). Ecosystems affected: npm.

How do I fix GHSA-hv53-3329-vmrm?

Update n8n to 1.118.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hv53-3329-vmrm is resolved across your whole dependency graph.

How do I detect GHSA-hv53-3329-vmrm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hv53-3329-vmrm if there is no patch (or I can't update yet)?

Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Is GHSA-hv53-3329-vmrm actively exploited in the wild?

No public exploit code has been indexed for GHSA-hv53-3329-vmrm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hv53-3329-vmrm?

GHSA-hv53-3329-vmrm has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hv53-3329-vmrm?

GHSA-hv53-3329-vmrm is classified as Unrestricted File Upload (CWE-434), CWE-693 (CWE-693). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hv53-3329-vmrm published, and has it been updated?

GHSA-hv53-3329-vmrm was published on February 4, 2026 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-hv53-3329-vmrm — n8n

GHSA-hv53-3329-vmrm is a Unrestricted File Upload vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

n8n Merge Node has Arbitrary File Write leading to RCE

Also known asCVE-2026-25056

Published

Feb 4, 2026

Updated

Feb 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hv53-3329-vmrm.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

37other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

n8nnpm

106Kdownloads / week

Description

Impact

A vulnerability in the Merge node's SQL Query mode allowed authenticated users with permission to create or modify workflows to write arbitrary files to the n8n server's filesystem potentially leading to remote code execution.

Patches

The issue has been fixed in n8n version 2.4.0, 1.118.0. Users should upgrade to this version or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Limit workflow creation and editing permissions to fully trusted users only.
Disable or restrict use of the Merge node if not essential for operations.
Review workflows for suspicious use of the Merge node's SQL Query mode.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Resources

n8n Documentation — Blocking nodes — how to globally disable specific nodes

n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility.

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n`	all versions	1.118.0`npm install n8n@1.118.0`
📦npm	`n8n`	≥ 2.0.0&&< 2.4.0	2.4.0`npm install n8n@2.4.0`

Affected Products

1 product · 2 configurations

Application

n8nn8n

≥ 2.0.0 && < 2.4.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n to 1.118.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hv53-3329-vmrm is resolved across your whole dependency graph.
Workarounds
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

## Impact A vulnerability in the Merge node's SQL Query mode allowed authenticated users with permission to create or modify workflows to write arbitrary files to the n8n server's filesystem potentially leading to remote code execution. ## Patches The issue has been fixed in n8n version 2.4.0, 1.118.0. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Disabl

O3 Security · Impact-Aware SCA

Is GHSA-hv53-3329-vmrm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

GHSA-hv53-3329-vmrm — n8n

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Workarounds

Resources

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-hv53-3329-vmrm in your dependencies?