CVE-2026-44789
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.43, 2.22.1, and 2.20.7, an authenticated user with permission to create or modify workflows could achieve global prototype pollution via an unvalidated pagination parameter in the HTTP Request node. Combined with other techniques this could lead to RCE on the instance. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.
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 confidencen8n workflow automation platform versions prior to 1.123.43, 2.22.1, and 2.20.7 contain a global prototype pollution vulnerability in the HTTP Request node. An authenticated user with workflow creation/modification permissions can inject arbitrary properties into JavaScript Object.prototype via an unvalidated pagination parameter, which when chained with additional exploitation techniques can lead to remote code execution.
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.43>= 2.0.0, < 2.20.7>= 2.21.0, < 2.22.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed n8n versionRun the command `n8n --version` or check the version in the package.json file of your n8n installation directory. If using Docker, run `docker exec <container> n8n --version`.Affected if The version is less than 1.123.43, or between 2.0.0 and 2.20.7, or between 2.21.0 and 2.22.1.
-
Verify HTTP Request node usageSearch your saved workflows for any nodes of type "n8n-nodes-base.httpRequest" or "@n8n/n8n-nodes-base.httpRequest". Use the n8n UI to list all workflows or query the database if you have direct access.Affected if Any workflow contains an HTTP Request node, as this is the vulnerable component.
-
Check HTTP Request node pagination settingsOpen workflows containing HTTP Request nodes and inspect each node's configuration. Navigate to the "Pagination" section within the node settings.Affected if Pagination is enabled and configured on any HTTP Request node, which exposes the vulnerable parameter.
-
Review user permissions for workflow editingCheck your n8n user management settings. Navigate to Settings > Users or query the users table in the database for roles with permissions including "workflow:create" or "workflow:update".Affected if Any authenticated user has permission to create or modify workflows, as the attacker needs this access.
-
Inspect for prototype pollution artifactsIf you suspect exploitation, check your n8n instance logs for unusual errors. You can also evaluate `Object.prototype` in a workflow expression (e.g., in a Set node using `={{ $json.someUnexpectedProperty }}`) to see if unexpected properties exist.Affected if JavaScript's Object.prototype contains unexpected properties that were not intentionally added, indicating possible exploitation.
You are affected if your n8n version falls within the vulnerable ranges AND you have workflows using the HTTP Request node with pagination enabled, combined with users who have workflow creation or modification permissions.
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.432.20.72.22.1
Upgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 or later. Restrict workflow creation/modification permissions to trusted users pending the upgrade.
1.123.43 (for 1.x users); 2.20.7 or 2.22.1 (for 2.x users)
- Identify your current n8n version by checking the instance or running `n8n --version`
- If running version 1.x (e.g., 1.0.0 to 1.123.42), upgrade to version 1.123.43 or later (e.g., latest 1.x release)
- If running version 2.x and between 2.0.0 and 2.20.6, upgrade to version 2.20.7 or later
- If running version 2.x and between 2.21.0 and 2.22.0, upgrade to version 2.22.1 or later
- After upgrading, verify the n8n service is running correctly and test that workflows with HTTP Request nodes function as expected
- Review workflow permissions to ensure only trusted users have create/modify access to workflows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44789 — 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-44789 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