dbcve.org
N8nApplication

CVE-2026-54314

HIGH · 7.5 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 2.24.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
n8n is an open source workflow automation platform. Prior to 2.24.0, 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. This vulnerability is fixed in 2.24.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Compression node's Decompress operation in n8n versions prior to 2.24.0 lacks bounds checking on decompressed output size, allowing a small compressed archive (zip bomb) to exhaust memory when processed. An unauthenticated attacker can trigger this via a public webhook workflow, causing the n8n process to crash and disrupt all workflows in the instance.

MitigationUpgrade n8n to version 2.24.0 or later. As a temporary measure, disable or restrict the Decompress operation in public-facing webhook workflows until the upgrade can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 2.24.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed n8n version
    Run `n8n --version` from the command line, or check the version displayed in the n8n UI footer, or query the API endpoint `/rest/version`
    Affected if The installed version is lower than 2.24.0
  2. Locate workflows using the Compression node Decompress operation
    In the n8n UI, search for workflows containing the 'Decompress' operation of the Compression node, or query the workflows API endpoint `/rest/workflows` and inspect node types
    Affected if Active workflows contain a Compression node with Decompress operation enabled
  3. Identify public webhook workflows using Decompress
    Review the workflows found in the previous step and check if they are activated and reachable via public webhook URLs (check the webhook settings for each workflow)
    Affected if A workflow with Decompress operation is exposed as a public webhook URL accessible without authentication
  4. Verify memory consumption during Decompress operations
    Monitor the n8n process memory usage when processing compressed input through the Decompress operation, or review system logs for out-of-memory events occurring after processing compressed data
    Affected if Memory spikes significantly during Decompress operations with small compressed inputs, indicating lack of bounds checking

A user is affected if their n8n instance version is below 2.24.0 AND they have active workflows using the Compression node's Decompress operation exposed via public webhooks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.24.0 or later
Fixed in 2.24.0
Interim mitigation

Upgrade n8n to version 2.24.0 or later. As a temporary measure, disable or restrict the Decompress operation in public-facing webhook workflows until the upgrade can be applied.

Recommended fix High confidence

2.24.0

  1. Ensure you have a backup of your n8n instance data and configuration
  2. Stop the n8n service
  3. Update n8n to version 2.24.0 or later. For Docker: `docker pull n8nio/n8n:latest` or specify version tag `2.24.0`
  4. For npm installation: `npm install -g [email protected]`
  5. For binary installations: download and install the 2.24.0 release from the n8n releases page
  6. Verify the installed version with `n8n --version`
  7. Restart the n8n service
  8. Test that workflows using the Compression node's Decompress operation function correctly
Caveat None specifically mentioned in the advisory for this security fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54314 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data