dbcve.org
N8nApplication

CVE-2026-54306

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 2.25.7 / 2.26.2 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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.25.7 and 2.26.2, a prototype pollution vulnerability allowed a crafted public webhook payload to inject attacker-controlled fields into workflow data during internal object copying. These fields could be surfaced and consumed as normal values by downstream built-in nodes. Where a workflow combines a public webhook with action nodes that consume the resulting fields, an attacker could cause the workflow to act as a confused deputy — targeting unintended records or issuing outbound requests using the workflow owner's configured credentials. This vulnerability is fixed in 2.25.7 and 2.26.2.

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

A prototype pollution vulnerability in n8n versions prior to 2.25.7 and 2.26.2 allows attackers sending crafted public webhook payloads to inject attacker-controlled fields into workflow data during internal object copying. These malicious fields can be surfaced and consumed as normal values by downstream built-in nodes, enabling a confused deputy attack where the workflow performs actions on unintended targets using the workflow owner's configured credentials.

MitigationUpgrade n8n to version 2.25.7 or 2.26.2. Additionally, consider implementing input validation on webhook receivers to reject payloads containing prototype-polluting property names (e.g., __proto__, constructor, prototype) and apply least-privilege principles to credentials used in workflows exposed to public webhooks.

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.25.7>= 2.26.0, < 2.26.2

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 n8n version
    Run `n8n --version` from the command line, or check the version displayed in the n8n UI footer at the bottom of any page
    Affected if The installed version is less than 2.25.7, or is 2.26.0 or 2.26.1
  2. Confirm public webhook usage
    In the n8n UI, navigate to the webhook nodes in your workflows and verify if any are set to 'Public' (GET/POST endpoints). You can also list webhook routes via the API endpoint `/webhook` or `/webhook-test`
    Affected if Any workflow contains a webhook node configured as a public endpoint that accepts unauthenticated requests
  3. Inspect webhook workflow configurations
    Review each workflow that has a public webhook node. Look for any nodes downstream that copy, merge, or process incoming webhook data (such as Set, Move Binary Data, or any code nodes using the received JSON)
    Affected if The workflow copies incoming webhook payload data into internal objects without sanitizing property names

You are affected if your n8n version is below 2.25.7 or between 2.26.0 and 2.26.1 AND you have workflows with public webhooks that process incoming JSON data.

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.25.7 / 2.26.2 or later
Fixed in 2.25.72.26.2
Interim mitigation

Upgrade n8n to version 2.25.7 or 2.26.2. Additionally, consider implementing input validation on webhook receivers to reject payloads containing prototype-polluting property names (e.g., __proto__, constructor, prototype) and apply least-privilege principles to credentials used in workflows exposed to public webhooks.

Recommended fix High confidence

2.25.7 (for 2.25.x users) or 2.26.2 (for 2.26.x users)

  1. Identify your current n8n version by checking the instance or running 'n8n --version'
  2. If running version < 2.25.7, plan upgrade to version 2.25.7
  3. If running version >= 2.26.0 and < 2.26.2, plan upgrade to version 2.26.2
  4. Backup your n8n instance, including workflows and configuration
  5. Upgrade n8n to the appropriate fixed version using your deployment method (npm, Docker, etc.)
  6. After upgrade, review workflows that use public webhooks for any anomalous data
  7. Monitor for any suspicious activity in workflows that combine public webhooks with action nodes
Caveat Review the n8n release notes for 2.25.7 and 2.26.2 to check for any breaking changes relevant to your workflows

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

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54306 — 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-54306 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