ImageMagick before 7.1.2-35 and 6.9.13-60 Infinite Loop via SVG Decoder
ImageMagick 7.0.0 before 7.1.2-35 and 6.x before 6.9.13-60 can hang on a crafted SVG image. Fixed in 7.1.2-35 and 6.9.13-60.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.1.2-35, 6.9.13-60
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. ImageMagick versions before 7.1.2-35 (7.x branch) or before 6.9.13-60 (6.x branch) The SVG decoder must process the attacker-supplied image
- Last modified
- 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? →
- 15/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
ImageMagick, an image-processing library, has a flaw in its SVG decoder that lets an attacker make it loop endlessly, consuming CPU and hanging the decoding process. An attacker can trigger this remotely by supplying a crafted SVG image, but they must have low-privilege login access to the system.
Read the original description
ImageMagick before 7.1.2-35 and 6.9.13-60 contains an infinite loop vulnerability in the SVG decoder because QueueAuthenticPixelCacheNexus in MagickCore/cache.c fails to validate requested region width and height. Attackers can supply a crafted SVG image that repeatedly requests a non-advancing pixel region, consuming CPU and hanging the decoding worker.
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.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
ImageMagick versions before 7.1.2-35 (7.x branch) or before 6.9.13-60 (6.x branch) The SVG decoder must process the attacker-supplied imageUpgrade to a fixed version: 7.1.2-35, 6.9.13-60.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ImageMagick ImageMagick
From 7.0.0 · fixed in 7.1.2-35; fixed in 6.9.13-60
Evidence 7
- Advisory
- Patch
- Patch
- Repository
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123273
Is CVE-2026-123273 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?
A crafted SVG image can make ImageMagick's SVG decoder enter an infinite loop. The loop uses CPU and hangs the decoding worker, which is a denial of service.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-123273?
ImageMagick: from 7.0.0 before 7.1.2-35; before 6.9.13-60.Source: cve.now feed data
Am I affected, and how do I check?
ImageMagick 7.x from 7.0.0 before 7.1.2-35 and 6.x before 6.9.13-60 are affected, and only when the SVG decoder processes the image. Check the installed version with the command magick -version, or convert -version on older installs.Source: vulncheck.com, github.com
How do I fix CVE-2026-123273?
Upgrade to ImageMagick 7.1.2-35 or later on the 7.x branch, or to 6.9.13-60 or later on the 6.x branch.Source: vulncheck.com, github.com