CVE-2026-103251: n8n: queue-mode package install bypass via Redis

HIGH
Published October 1, 2026
CISO Take

n8n queue-mode deployments contain a validation bypass in the community package installer: anyone who can write to the Redis pub/sub channel can make every worker and main instance install arbitrary npm packages, skipping name validation, permission checks, checksum verification and npm safety checks. That is effectively cluster-wide remote code execution on the machines that hold your AI agent workflows, API keys and connected-system credentials. Exploitation requires adjacent-network access and Redis write access, which keeps the CVSS at 7.1 and EPSS at 0.2%, but the 91st percentile still puts it above most CVEs. It is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later. Until then, restrict Redis to the n8n hosts only, enforce authentication and TLS on it, and audit installed community packages.

Sources:NVDEPSSGitHub Advisoryvulncheck.comATLASOpenSSFCISA SSVC

What is the risk?

Overall risk is HIGH for queue-mode deployments with weak Redis exposure, and low for single-instance deployments. The attack is of high complexity: it needs adjacent-network position and write access to Redis, such as an unauthenticated Redis instance, a flat network or a compromised neighbouring host. Once that precondition holds, no n8n credentials are needed (the description says without authentication) and the result is arbitrary code execution with high impact on confidentiality, integrity and availability across all instances. There is no known in-the-wild exploitation or public PoC. The package's 244 other CVEs show a large attack surface, and its 6.7 OpenSSF Scorecard is only moderate. Treat Redis as a trust boundary: whoever controls it controls the whole cluster.

How does the attack unfold?

Initial Access
Attacker obtains an adjacent-network position with write access to the Redis instance used by the n8n queue-mode cluster.
AML.T0012
Exploitation
A crafted package-install message published over pub/sub bypasses name, permission, checksum and npm safety checks.
AML.T0010.005
Execution
Every main and worker instance installs and loads the attacker-controlled npm package, running code on the whole cluster.
AML.T0011.001
Impact
Attacker harvests stored LLM and integration credentials, tampers with AI agent workflows and exfiltrates pipeline data.
AML.T0083

What systems are affected?

PackageEcosystemVulnerable RangePatched
n8nnpm—No patch
210.5KOpenSSF 7.116 dependentsPushed 3d ago42% patched~19d to patchFull package profile →

Do you use n8n? You're affected.

How severe is it?

CVSS 3.1
7.1 / 10
EPSS
0.2%
chance of exploitation in 30 days
Higher than 10% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Moderate

What is the attack surface?

AVACPRUISCIA
AVAdjacent
ACHigh
PRLow
UINone
SUnchanged
CHigh
IHigh
AHigh

What should I do?

6 steps
  1. Patch: upgrade to n8n 1.123.80 or later on the 1.x line, 2.39.6 or later on 2.0.0 to 2.39.x, or 2.40.1 or later on 2.40.x, across all main and worker instances at once.

  2. Lock down Redis: require authentication and ACLs, enable TLS, bind to private interfaces, and allow access only from n8n hosts via firewall or security groups.

  3. Segment the network so adjacent hosts cannot reach the Redis port.

  4. If you cannot patch yet, disable community package installation if your configuration allows it.

  5. Detect: inventory installed community packages on every node and compare them to an approved list. Alert on unexpected npm install activity or child processes spawned by n8n, and on new outbound connections from workers. Review Redis logs and MONITOR or ACL logs for unexpected publishers on n8n channels.

  6. If compromise is suspected, rotate all credentials stored in n8n and the n8n encryption key.

What does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableNo
Technical Impacttotal

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Article 15-Accuracy, robustness and cybersecurity
ISO 42001
A.10.3-Suppliers
NIST AI RMF
GOVERN 6.1-Policies and procedures for third-party AI risksMANAGE 2.3-Procedures to respond to and recover from unknown risks
OWASP LLM Top 10
LLM03-Supply ChainLLM06-Excessive Agency

Frequently Asked Questions

What is CVE-2026-103251?

n8n queue-mode deployments contain a validation bypass in the community package installer: anyone who can write to the Redis pub/sub channel can make every worker and main instance install arbitrary npm packages, skipping name validation, permission checks, checksum verification and npm safety checks. That is effectively cluster-wide remote code execution on the machines that hold your AI agent workflows, API keys and connected-system credentials. Exploitation requires adjacent-network access and Redis write access, which keeps the CVSS at 7.1 and EPSS at 0.2%, but the 91st percentile still puts it above most CVEs. It is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK. Upgrade to n8n 1.123.80, 2.39.6 or 2.40.1 or later. Until then, restrict Redis to the n8n hosts only, enforce authentication and TLS on it, and audit installed community packages.

Is CVE-2026-103251 actively exploited?

No confirmed active exploitation of CVE-2026-103251 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-103251?

1. Patch: upgrade to n8n 1.123.80 or later on the 1.x line, 2.39.6 or later on 2.0.0 to 2.39.x, or 2.40.1 or later on 2.40.x, across all main and worker instances at once. 2. Lock down Redis: require authentication and ACLs, enable TLS, bind to private interfaces, and allow access only from n8n hosts via firewall or security groups. 3. Segment the network so adjacent hosts cannot reach the Redis port. 4. If you cannot patch yet, disable community package installation if your configuration allows it. 5. Detect: inventory installed community packages on every node and compare them to an approved list. Alert on unexpected npm install activity or child processes spawned by n8n, and on new outbound connections from workers. Review Redis logs and MONITOR or ACL logs for unexpected publishers on n8n channels. 6. If compromise is suspected, rotate all credentials stored in n8n and the n8n encryption key.

What systems are affected by CVE-2026-103251?

This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation, queue-mode distributed deployments, LLM orchestration pipelines, RAG pipelines.

What is the CVSS score for CVE-2026-103251?

CVE-2026-103251 has a CVSS v3.1 base score of 7.1 (HIGH). The EPSS exploitation probability is 0.20%.

What is the AI security impact?

Affected AI Architectures

agent frameworksworkflow automationqueue-mode distributed deploymentsLLM orchestration pipelinesRAG pipelines

MITRE ATLAS Techniques

AML.T0010.001AI Software
AML.T0010.005AI Agent Tool
AML.T0011.001Malicious Package
AML.T0050Command and Scripting Interpreter
AML.T0083Credentials from AI Agent Configuration

Compliance Controls Affected

EU AI Act: Article 15
ISO 42001: A.10.3
NIST AI RMF: GOVERN 6.1, MANAGE 2.3
OWASP LLM Top 10: LLM03, LLM06

What are the technical details?

Original Advisory

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a validation bypass vulnerability in the community package installation handler for queue mode deployments. Attackers with Redis write access can bypass name validation, permission checks, checksum verification, and npm safety checks to install arbitrary npm packages across all cluster instances without authentication.

Exploitation Scenario

An attacker gains a foothold on a host in the same network segment as a self-hosted n8n queue-mode cluster, for example via a compromised container or a misconfigured VPC. They find the Redis instance used for n8n queues has weak or no authentication. They publish a crafted community-package install message to the pub/sub channel, naming a malicious npm package they control. Every main and worker instance accepts it without name validation, permission checks, checksum verification or npm safety checks, then installs and loads the package. The package runs with the n8n process privileges, harvests LLM API keys, vector DB credentials and OAuth tokens from the credential store, and opens a persistent reverse shell. The attacker can then alter AI agent workflows to exfiltrate data or abuse the connected tools.

Weaknesses (CWE)

CWE-862 — Missing Authorization: The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

  • [Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • [Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Timeline

Published
October 1, 2026
Last Modified
October 1, 2026
First Seen
October 1, 2026

Related Vulnerabilities