## Impact The Compression node's Decompress operation expanded attacker-controlled archives into memory without enforcing limits on decompressed output size. An unauthenticated attacker could send a small compressed archive to a public webhook workflow using this node, causing the n8n process to terminate due to memory exhaustion and disrupting all workflows in the same instance. ## Patches The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability. The fix introduces configurable limits on decompressed output size (`N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES`) and ZIP entry count (`N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES`). ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable the Compression node by adding `n8n-nodes-base.compression` to the `NODES_EXCLUDE` environment variable. - Restrict public webhook workflows that accept archive file uploads to authenticated endpoints only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
## Impact The Compression node's Decompress operation expanded attacker-controlled archives into memory without enforcing limits on decompressed output size. An unauthenticated attacker could send a small compressed archive to a public webhook workflow using this node, causing the n8n process to terminate due to memory exhaustion and disrupting all workflows in the same instance. ## Patches The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability. The fix introduces configurable limits on decompressed output size (`N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES`) and ZIP entry count (`N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES`). ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable the Compression node by adding `n8n-nodes-base.compression` to the `NODES_EXCLUDE` environment variable. - Restrict public webhook workflows that accept archive file uploads to authenticated endpoints only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Update n8n to 2.24.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scann8n: Denial of Service via ZIP decompression in webhook workflow affects n8n (npm). Severity is high. ## Impact The Compression node's Decompress operation expanded attacker-controlled archives into memory without enforcing limits on decompressed output size. An unauthenticated attacker could send a small compressed archive to a public webhook workflow using this node, causing the n8n process to terminate due to memory exhaustion and disrupting all workflows in the same instance. ## Patches The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability. The fix introduces configurable limits on decompressed output size (`N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES`) and ZIP entry count (`N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES`). ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable the Compression node by adding `n8n-nodes-base.compression` to the `NODES_EXCLUDE` environment variable. - Restrict public webhook workflows that accept archive file uploads to authenticated endpoints only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
AI coding agents often install or upgrade packages automatically in npm. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| n8nnpm | <2.24.0 | 2.24.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate n8n to 2.24.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scann8n: Denial of Service via ZIP decompression in webhook workflow affects n8n (npm). Severity is high. ## Impact The Compression node's Decompress operation expanded attacker-controlled archives into memory without enforcing limits on decompressed output size. An unauthenticated attacker could send a small compressed archive to a public webhook workflow using this node, causing the n8n process to terminate due to memory exhaustion and disrupting all workflows in the same instance. ## Patches The issue has been fixed in n8n version 2.24.0. Users should upgrade to this version or later to remediate the vulnerability. The fix introduces configurable limits on decompressed output size (`N8N_COMPRESSION_NODE_MAX_DECOMPRESSED_SIZE_BYTES`) and ZIP entry count (`N8N_COMPRESSION_NODE_MAX_ZIP_ENTRIES`). ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Disable the Compression node by adding `n8n-nodes-base.compression` to the `NODES_EXCLUDE` environment variable. - Restrict public webhook workflows that accept archive file uploads to authenticated endpoints only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
AI coding agents often install or upgrade packages automatically in npm. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| n8nnpm | <2.24.0 | 2.24.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard