CVE
n8n remote code execution via bundled GraphicsMagick
Affects n8n instances running the official Docker image, which bundles a GraphicsMagick version with known vulnerabilities, when the Edit Image node processes untrusted images. Fixed in 1.123.89, 2.45.5, 2.46.1 and 3.0.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.123.89, 2.46.1, 2.45.5, 3.0.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Runs the official n8n Docker image, which bundles the affected GraphicsMagick version An Edit Image node processes untrusted images, for example from a Webhook-fed workflow
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- 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
Summary
n8n's official Docker image bundles a GraphicsMagick version with known vulnerabilities, which the Edit Image node uses to process images. A remote attacker with low-privilege login access can supply crafted untrusted images to an Edit Image workflow, such as one fed by a Webhook node, and execute code on the n8n instance.
Read the original description
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.
Who should check
Teams running self-hosted n8n from the official Docker image with Edit Image workflows that process untrusted images, such as Webhook-fed workflows
Read the source excerpt
“bundles a GraphicsMagick version with known vulnerabilities in its official Docker image”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Runs the official n8n Docker image, which bundles the affected GraphicsMagick version An Edit Image node processes untrusted images, for example from a Webhook-fed workflowUpgrade to a fixed version: 1.123.89, 2.46.1, 2.45.5, 3.0.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126384 (n8n before 1.123.89 RCE via Bundled GraphicsMagick in Edit Image Node), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126384 (entry last updated 2026-11-13):
Affected:
- n8n-io n8n: fixed in 1.123.89
- n8n-io n8n: from 2.46.0, fixed in 2.46.1
- n8n-io n8n: from 2.0.0, fixed in 2.45.5
- n8n-io n8n: from 3.0.0, fixed in 3.0.1
Fixed versions: 1.123.89, 2.46.1, 2.45.5, 3.0.1.
Conditions (all must be true for the bug to be hit):
- Runs the official n8n Docker image, which bundles the affected GraphicsMagick version (source: https://www.vulncheck.com/advisories/n8n-before-1.123.89-rce-via-bundled-graphicsmagick-in-edit-image-node)
- An Edit Image node processes untrusted images, for example from a Webhook-fed workflow (source: https://github.com/n8n-io/n8n/security/advisories/GHSA-f2cw-9483-7vcp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126384 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126384 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/n8n-io/n8n/security/advisories/GHSA-f2cw-9483-7vcp
- https://www.vulncheck.com/advisories/n8n-before-1.123.89-rce-via-bundled-graphicsmagick-in-edit-image-node
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126384
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126384"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- n8n-io n8n
fixed in 1.123.89
- n8n-io n8n
From 2.46.0 · fixed in 2.46.1
- n8n-io n8n
From 2.0.0 · fixed in 2.45.5
- n8n-io n8n
From 3.0.0 · fixed in 3.0.1
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126384
Is CVE-2026-126384 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Processing untrusted images with the Edit Image node could lead to remote code execution on the n8n instance. The cause is a GraphicsMagick version bundled in the official n8n Docker image that has known vulnerabilities.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126384?
n8n: before 1.123.89. n8n: from 2.46.0 before 2.46.1. n8n: from 2.0.0 before 2.45.5. n8n: from 3.0.0 before 3.0.1.Source: cve.now feed data
Am I affected, and how do I check?
Affected n8n versions are those before 1.123.89, 2.0.0 through 2.45.5, 2.46.0 through 2.46.1, and 3.0.0 through 3.0.1. To check, look at the installed n8n version and whether the Edit Image node is used on untrusted images, such as images from a Webhook-fed workflow.Source: vulncheck.com, github.com
How do I fix CVE-2026-126384?
Upgrade to the fixed version for your release line: 1.123.89, 2.45.5, 2.46.1, or 3.0.1. The sources provided do not list a workaround.Source: vulncheck.com, github.com