UTC
Medium

OData $filter Injection in Microsoft Outlook and SharePoint v1 Nodes

GHSA-mgpr-56r4-5c67 · published 2026-10-14

Severity
Medium
CVSS score
5.3
Chance of exploitation (EPSS)
No CVE
Fixed in
2.44.1
What it is

The Microsoft Outlook contact lookup and the Microsoft SharePoint v1 item update build an OData $filter string literal from an expression-bindable parameter without escaping it. A single quote in the value closes the literal and rewrites the query. Where a workflow binds untrusted input into those fields, the Outlook lookup returns the bound mailbox's entire contact list instead of one contact, and the SharePoint pre-write lookup can be redirected so the node writes the submitted field values onto a list item the workflow never intended, both within the scope of the stored credential.

What to do

Upgrade n8n to 2.44.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The issue has been fixed in n8n versions 1.123.85, 2.44.1, and 2.43.5. Users should upgrade to one of these versions or later to remediate the vulnerability.

If you cannot upgrade yet

If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Audit active workflows that use the Microsoft Outlook contact getAll operation or the 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 that feed into these workflows. Deactivate affected workflows until the instance is patched. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.851.123.85
n8nnpm< 2.43.52.43.5
n8nnpm< 2.44.12.44.1

The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].