CVE-2026-126384: n8n before 1.123.89 RCE via Bundled GraphicsMagick in Edit Image Node

Q: Which deployments are exposed to this issue?

Deployments using the official n8n Docker image are exposed if they run a version before 1.123.89, a 2.x version before 2.45.5, a 2.46.x version before 2.46.1, or a 3.x version before 3.0.1 and use the Edit Image node to process attacker-controlled images.

Q: What does an attacker need to exploit it?

An attacker needs a way to provide a crafted untrusted image to an Edit Image workflow. A workflow that accepts images through a Webhook node is an example of an exploitable input path; the attacker does not need user interaction, but the CVSS vector indicates low privileges are required.

Q: How can I determine whether a workflow is at risk?

Review workflows for Edit Image nodes and trace their image inputs. Treat a workflow as at risk when an untrusted party can supply the image, including through a webhook-fed workflow, and the instance uses an affected official Docker image version.

Q: What should be prioritized for remediation?

Upgrade affected n8n Docker deployments to 1.123.89, 2.45.5, 2.46.1, or 3.0.1 or later within the applicable release line. Until upgraded, prevent untrusted sources from reaching Edit Image nodes, especially webhook-based image ingestion paths.

Published Nov 13, 2026

Updated

n8n before 1.123.89, 2.x before 2.45.5, 2.46.x before 2.46.1, and 3.x before 3.0.1 bundles a GraphicsMagick version with known vulnerabilities in its official Docker image, which the Edit Image node uses to process images. Attackers who can supply crafted untrusted images to an Edit Image workflow, such as one fed by a Webhook node, can execute code on the n8n instance.

Affected Software

1 affected component

n8n n8n<1.123.89, <2.45.5, <2.46.1, <3.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade n8n to a version that resolves this vulnerability.
Fixed in 1.123.89
Upgrade
Upgrade n8n to a version that resolves this vulnerability.
Fixed in 2.45.5
Upgrade
Upgrade n8n to a version that resolves this vulnerability.
Fixed in 2.46.1
Upgrade
Upgrade n8n to a version that resolves this vulnerability.
Fixed in 3.0.1

Event History

Nov 13, 2026

CVE Published

via MITRE·09:35 AM

Data Sourced

via MITRE·09:35 AM

DescriptionSeverityWeakness

Data Sourced

via NVD·10:17 AM

DescriptionSeverity

Frequently Asked Questions

Which deployments are exposed to this issue?

Deployments using the official n8n Docker image are exposed if they run a version before 1.123.89, a 2.x version before 2.45.5, a 2.46.x version before 2.46.1, or a 3.x version before 3.0.1 and use the Edit Image node to process attacker-controlled images.

What does an attacker need to exploit it?

An attacker needs a way to provide a crafted untrusted image to an Edit Image workflow. A workflow that accepts images through a Webhook node is an example of an exploitable input path; the attacker does not need user interaction, but the CVSS vector indicates low privileges are required.

How can I determine whether a workflow is at risk?

Review workflows for Edit Image nodes and trace their image inputs. Treat a workflow as at risk when an untrusted party can supply the image, including through a webhook-fed workflow, and the instance uses an affected official Docker image version.

What should be prioritized for remediation?

Upgrade affected n8n Docker deployments to 1.123.89, 2.45.5, 2.46.1, or 3.0.1 or later within the applicable release line. Until upgraded, prevent untrusted sources from reaching Edit Image nodes, especially webhook-based image ingestion paths.

CVE-2026-126384: n8n before 1.123.89 RCE via Bundled GraphicsMagick in Edit Image Node

Affected Software

Remediation

Event History

Frequently Asked Questions

Which deployments are exposed to this issue?

What does an attacker need to exploit it?

How can I determine whether a workflow is at risk?

What should be prioritized for remediation?

Company

Resources

Contact

Frequently Asked Questions

Which deployments are exposed to this issue?

What does an attacker need to exploit it?

How can I determine whether a workflow is at risk?

What should be prioritized for remediation?