# CVE-2026-123273: ImageMagick before 7.1.2-35 and 6.9.13-60 Infinite Loop via SVG Decoder


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 5 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-123273, ECHO-5378-ed14-3532, GHSA-5w78-w8pm-578p, GHSA-q66g-3m63-78mh, UBUNTU-CVE-2026-123273, openSUSE-SU-2026:12508-1

## What is CVE-2026-123273?

CVE-2026-123273 is a high-severity vulnerability in ImageMagick, published on 5 Nov 2026. 

### Official 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.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-123273?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ImageMagick` | openSUSE:Tumbleweed | All versions | 7.1.2.35-2.1 |

## How do I fix CVE-2026-123273?

Upgrade to a fixed version.

## Is CVE-2026-123273 being exploited?

There is no known exploitation of CVE-2026-123273 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123273 and fix it if it is affected.

What it is: CVE-2026-123273 is a high-severity vulnerability in ImageMagick, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123273 in the wild and no public exploit code.

Affected product: ImageMagick. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123273/ (Markdown: https://insights.sbomify.com/CVE-2026-123273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123273
- OSV: https://osv.dev/vulnerability/CVE-2026-123273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123273/
Summaries are generated and may contain mistakes; the official description above is the record.