CVE-2026-59206
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 · uneditedn8n is an open source workflow automation platform. Prior to 1.123.61, 2.27.4, and, 2.28.1, an authenticated user with the default workflow:create permission could pollute Object.prototype through a crafted workflow saved, updated, or imported via the workflow API, allowing unauthenticated requests to be treated as a privileged user and exposing user and project listing endpoints. This issue is fixed in versions 1.123.61, 2.27.4, and 2.28.1.
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 confidenceAn authenticated user with workflow:create permission can inject properties into Object.prototype via crafted workflow data saved, updated, or imported through the workflow API. This prototype pollution causes subsequent unauthenticated requests to be treated as privileged users, enabling unauthorized access to user and project listing endpoints.
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< 1.123.61>= 2.0.0, < 2.27.4= 2.28.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify n8n versionCheck the installed n8n version by inspecting the package.json, running 'n8n --version' CLI command, or checking the About page in the n8n UIAffected if The installed version is less than 1.123.61, OR between 2.0.0 and 2.27.3 inclusive, OR exactly 2.28.0
-
Verify workflow:create permission existsReview user roles and permissions in n8n to identify accounts with the workflow:create permission enabledAffected if Any user account possesses the workflow:create permission on a vulnerable n8n version
-
Audit existing workflows for prototype pollutionExport or list all workflows via the API and inspect workflow JSON data for unexpected properties at the top level, particularly __proto__, constructor, or any key that could override Object.prototype propertiesAffected if Any workflow contains suspicious keys like '__proto__', 'constructor', or unusual property names that could pollute the prototype
-
Review API access logsExamine n8n and reverse proxy logs for requests to user and project listing endpoints that originate from unauthenticated or unexpected sourcesAffected if Unauthenticated requests are accessing privileged endpoints or requests are succeeding without proper authentication headers
A user is affected if running a vulnerable n8n version AND has users with workflow:create permission, with workflows potentially containing malicious prototype-polluting properties allowing privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.123.612.27.4
Upgrade n8n to version 1.123.61, 2.27.4, or 2.28.1. If immediate patching is not feasible, temporarily restrict or audit users with workflow:create permissions and monitor API access logs.
Upgrade to n8n 1.123.61 (for 1.x users), 2.27.4 (for 2.0.0-2.27.x users), or 2.28.1 (for 2.28.0 users)
- 1. Backup your n8n instance (database, credentials, and configuration files) before upgrading
- 2. Determine your current n8n version by checking the running instance or package.json
- 3. If running version < 1.123.61: upgrade to version 1.123.61
- 4. If running version >= 2.0.0 and < 2.27.4: upgrade to version 2.27.4
- 5. If running version 2.28.0: upgrade to version 2.28.1
- 6. Restart the n8n service after upgrade
- 7. Verify the upgrade was successful by checking the version number and testing workflow creation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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