This is your bi-weekly security update from n8n. The following security advisories have been published since our last update:
- Severity: High | Deprecated Code Nodes Allow Code Execution in the n8n Main Process — GHSA-9p7v-45m2-wxgj
- Severity: High | Insecure GraphicsMagick Configuration — GHSA-f2cw-9483-7vcp
- Severity: High | Insufficient Isolation in Workflow Expression Evaluation — GHSA-gx3v-3x3v-f8r5
- Severity: Medium | Browser Use Upload Tool Reads Arbitrary Files from the n8n Server — GHSA-9qx8-fhxv-w794
- Severity: Medium | Chat Trigger Embedded Chat Does Not Enforce n8n User Auth on All Requests — GHSA-pwj5-wwm6-g83j
- Severity: Medium | MongoDB Node Update Operations Can Modify Unintended Documents — GHSA-4v22-g448-h4rg
- Severity: Medium | OAuth Account Hijack in the End-User Credential Connect Flow via Unauthenticated Callback — GHSA-426f-xmcv-g8pg
- Severity: Medium | Open Redirect via MCP OAuth Dynamic Client Registration — GHSA-rc3w-8jc8-7x3w
- Severity: Medium | Asana Trigger: Unauthenticated Request Can Reset Webhook Verification Secret — GHSA-mx4r-96jx-v278
- Severity: Medium | SQL Injection via Metadata Filter Key in the Vector Store (OracleDB) Node — GHSA-2x68-96jw-5r6c
- Severity: Medium | Credential-Using Nodes Forward Authentication Headers on Cross-Origin Redirects — GHSA-prmc-fg87-r4gh
- Severity: Medium | NocoDB Node Sends Its API Token to Attacker-Chosen Hosts When Downloading Attachments — GHSA-jmcg-c7p5-q69g
These vulnerabilities have been fixed in the following n8n versions:
- v1 patched in v1.123.89
- v3 patched in v3.0.1
- beta patched in v2.46.1
- stable patched in v2.45.5
What you need to do
If you are running a cloud version of n8n, your instance is patched automatically, and no action is required.
If you are running a self-hosted n8n instance on a version below the fixed versions listed above, we recommend upgrading at your earliest convenience.
- Upgrade guide: Update n8n | Deploy | n8n Docs
- Full advisory details: Security Advisories · n8n-io/n8n · GitHub
If you are already running the latest patch version for your release branch, no action is needed.
Staying up to date
These updates are part of our regular security communication cadence. If you don’t already, you can also opt in to receive these updates via email here.
Learn more about our security approach: How n8n Handles Vulnerability Disclosure - and Why We Do It This Way – n8n Blog
Best regards,
The n8n Security Team