UTC
High

Community Package Install Validation Bypass via PubSub in Queue Mode Deployments

GHSA-fmmv-p585-7c8x · published 2026-09-16

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
No CVE
Fixed in
2.40.1
What it is

In deployments using Redis for scaling (queue mode), the internal handler that installs a community package applied none of the checks the normal install path performs — name and prefix validation, the install-permission check, checksum verification, and the npm safety check. Anyone able to write to that Redis instance could have n8n download, install and load any npm package on every instance in the cluster, with no n8n account, while that action is otherwise restricted to the instance owner.

What to do

Upgrade n8n to 2.40.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.80, 2.39.6, and 2.40.1. 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 access to the Redis instance to only trusted n8n components, using authentication and network-level controls (firewall rules, private networking). Disable community package installation by setting N8N_COMMUNITY_PACKAGES_ENABLED=false if community nodes are not required. Audit installed community packages for any unexpected entries and remove them. Restrict n8n instance access to fully trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.801.123.80
n8nnpm< 2.39.62.39.6
n8nnpm< 2.40.12.40.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].