CVE-2026-118641: n8n OData $filter injection in Outlook and SharePoint nodes

CVE-2026-118641 · Severity: high · CVSS 7.5 · Published 2026-10-28

n8n is a workflow automation platform that connects business applications. The Microsoft Outlook contact lookup and SharePoint item update nodes fail to properly escape user input in database queries, allowing attackers to inject malicious code. An attacker who submits untrusted data to these workflow steps can steal an entire mailbox's contact list or overwrite unintended items in SharePoint lists that the workflow has access to.

Technologies: N8n. Vendors: N8n.

Quick answers

Is CVE-2026-118641 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-118641 being exploited in the wild.
How severe is CVE-2026-118641?
High severity, with a CVSS score of 7.5, published 28 October 2026.
Which products and versions are affected?
N8n before 1.123.85, 2.x before 2.43.5, 2.44.x before 2.44.1.
Is there a fix for CVE-2026-118641?
Yes: fixed in n8n 1.123.85, 2.43.5, 2.44.1. Until then: Restrict n8n instance access to fully trusted users only. Audit active workflows using the Microsoft Outlook contact getAll operation or Microsoft SharePoint v1 item update/upsert operation and remove any bindings that pass untrusted external data into the affected parameters. Apply network-level controls to restrict access to webhook endpoints feeding into these workflows, or deactivate affected workflows until patched.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-14"}, {"kind": "advisory", "at": "2026-10-28"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118641 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-118641?
Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: n8n 1.123.85, 2.43.5, 2.44.1

Restrict n8n instance access to fully trusted users only. Audit active workflows using the Microsoft Outlook contact getAll operation or Microsoft SharePoint v1 item update/upsert operation and remove any bindings that pass untrusted external data into the affected parameters. Apply network-level controls to restrict access to webhook endpoints feeding into these workflows, or deactivate affected workflows until patched.</anigation> <parameter name="timeline">[{"kind": "disclosed", "at": "2026-10-14"}, {"kind": "advisory", "at": "2026-10-28"}]

Technical details

An OData $filter injection vulnerability in n8n's Microsoft Outlook and SharePoint v1 nodes allows attackers to break out of string literals by injecting single quotes into expression-bindable parameters without proper escaping. Exploitation requires the attacker to control untrusted input bound to the vulnerable parameters in an active workflow; successful exploitation grants access to all contacts in the bound mailbox or the ability to write to unintended SharePoint list items within the scope of the stored credential.

Affected products

  • n8n n8n before 1.123.85, 2.x before 2.43.5, 2.44.x before 2.44.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.