CVE-2026-44789: n8n: HTTP Request Node Pagination Prototype Pollution to RCE

Published May 14, 2026
·
Updated

Impact 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.

Patches The issue has been fixed in n8n versions 1.123.43, 2.20.7, and 2.22.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Disable the HTTP Request node by adding n8n-nodes-base.httpRequest to the NODESEXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

--- n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backwards compatibility.

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

Other sources

n8n 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.

MITRE

Affected Software

6 affected componentsFixes available
npm/n8n>=2.0.0-rc.0<2.20.7
2.20.7
npm/n8n>=2.21.0<2.22.1
2.22.1
npm/n8n<1.123.43
1.123.43
n8n N8n Node.js<1.123.43
n8n N8n Node.js>=2.0.0<2.20.7
n8n N8n Node.js>=2.21.0<2.22.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.20.7
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.22.1
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.43
  4. Configuration

    Add 'n8n-nodes-base.httpRequest' to the NODES_EXCLUDE environment variable to disable the HTTP Request node.

    n8n NODES_EXCLUDE = n8n-nodes-base.httpRequest
  5. Configuration

    Limit workflow creation and editing permissions to fully trusted users only.

    n8n (access control) workflow_creation_and_editing_permissions = fully trusted users only

Event History

May 14, 2026
Advisory Published
via GitHub·04:17 PM
Data Sourced
via GitHub·04:17 PM
DescriptionWeaknessAffected Software
Jun 23, 2026
CVE Published
via MITRE·03:52 PM
Data Sourced
via MITRE·03:52 PM
DescriptionWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44789?

CVE-2026-44789 is considered a critical vulnerability due to the potential for remote code execution (RCE) via global prototype pollution.

2

How do I fix CVE-2026-44789?

To fix CVE-2026-44789, update to n8n version 1.123.43 or higher, 2.20.7, or 2.22.1.

3

What vulnerabilities are associated with CVE-2026-44789?

CVE-2026-44789 allows authenticated users to exploit unvalidated pagination parameters, potentially leading to RCE.

4

Who is affected by CVE-2026-44789?

Any authenticated user with permission to create or modify workflows in affected versions of n8n is vulnerable to CVE-2026-44789.

5

What does CVE-2026-44789 mean for my n8n instance?

CVE-2026-44789 indicates a serious threat that could allow attackers to execute code on your n8n instance if not mitigated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203