n8n before 1.123.85, 2.43.5, and 2.44.1 OData $filter Injection via Outlook and SharePoint Nodes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.123.85, 2.44.1, 2.43.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
n8n, an open-source workflow automation platform, is affected through its Microsoft Outlook and SharePoint nodes, which fail to properly sanitize input used in query filters. An attacker who can feed untrusted data into a workflow could read the full contact list of the connected mailbox or modify unintended SharePoint list items within the access granted by the stored credentials.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 contains an OData $filter injection vulnerability in the Microsoft Outlook contact lookup and Microsoft SharePoint v1 item update nodes, which build $filter string literals from expression-bindable parameters without escaping. Attackers who supply untrusted input to such workflows can inject single quotes to dump the bound mailbox's entire contact list or redirect SharePoint writes onto unintended list items within the stored credential's scope.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n8n-io n8n
fixed in 1.123.85
- n8n-io n8n
From 2.44.0 · fixed in 2.44.1
- n8n-io n8n
From 2.0.0 · fixed in 2.43.5