ImageMagick: Specially crafted SVG leads to segmentation fault and generate trash files in "/tmp", possible to leverage DoS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-1289: 0.86% estimated exploitation activity in the next 30 days; percentile 58.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Specially crafted SVG file make segmentation fault and generate trash files in "/tmp", possible to leverage DoS. Operating system, version and so on Linux, Debian (Buster) LTS core 5.10 / Parrot OS 5.1 (Electro Ara) Tested ImageMagick version 6.9.11-60, 7.1.0-62 Details A specially created SVG file that loads by itself and make segmentation fault. Remote attackers can take advantage of this vulnerability to cause a denial of service of the generated SVG file. It seems that this error affects a lot of websites and causes a generating trash files in when uploading this PC file to the server. I think it's better to check the file descriptor coming from itself before executing . PoC 1. Generate SVG file: 2. Run some commands for verification: Impact Possible DOS, because when ImageMagick crashes it generates a lot of trash files. This trash file can be large, if SVG file contains many render action. Additional impact In DOS attack if remount attacker uploads an SVG file of size…

Published by the source

12 Mar 2026, 20:30 UTC

Last modified by the source

12 Mar 2026, 20:30 UTC

Source last checked

26 Oct 2026, 17:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j96m-mjp6-99xr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-1289

Advisory: ImageMagick: Specially crafted SVG leads to segmentation fault and generate trash files in "/tmp", possible to leverage DoS
IDs: CVE-2023-1289, GHSA-j96m-mjp6-99xr
Record: https://patchnext.com/advisories/cve-2023-1289 (revision 1, source checked 26 Oct 2026, 17:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: magick.net-q8-arm64 13.0.0; magick.net-q8-x86 13.0.0; magick.net-q16-hdri-anycpu 13.0.0; magick.net-q16-openmp-x64 13.0.0; magick.net-q16-anycpu 13.0.0; magick.net-q16-hdri-x86 13.0.0; magick.net-q16-hdri-openmp-arm64 13.0.0; magick.net-q16-hdri-arm64 13.0.0; magick.net-q16-x86 13.0.0; magick.net-q8-openmp-x64 13.0.0; magick.net-q16-hdri-openmp-x64 13.0.0; magick.net-q16-openmp-arm64 13.0.0; magick.net-q16-x64 13.0.0; magick.net-q8-x64 13.0.0; magick.net-q8-openmp-arm64 13.0.0; magick.net-q8-anycpu 13.0.0; magick.net-q16-openmp-x86 13.0.0; magick.net-q16-arm64 13.0.0; magick.net-q16-hdri-x64 13.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet magick.net-q8-arm64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q8-x86: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-hdri-anycpu: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-openmp-x64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-anycpu: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-hdri-x86: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-hdri-openmp-arm64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-hdri-arm64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-x86: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q8-openmp-x64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-hdri-openmp-x64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-openmp-arm64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-x64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q8-x64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q8-openmp-arm64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q8-anycpu: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-openmp-x86: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-arm64: affected <= 12.3.0; fixed in 13.0.0
- NuGet magick.net-q16-hdri-x64: affected <= 12.3.0; fixed in 13.0.0

## Suggested inspection (read-only)
- NuGet magick.net-q8-arm64: check the installed version with your package manager.
- NuGet magick.net-q8-x86: check the installed version with your package manager.
- NuGet magick.net-q16-hdri-anycpu: check the installed version with your package manager.
- NuGet magick.net-q16-openmp-x64: check the installed version with your package manager.
- NuGet magick.net-q16-anycpu: check the installed version with your package manager.
- NuGet magick.net-q16-hdri-x86: check the installed version with your package manager.
- NuGet magick.net-q16-hdri-openmp-arm64: check the installed version with your package manager.
- NuGet magick.net-q16-hdri-arm64: check the installed version with your package manager.
- NuGet magick.net-q16-x86: check the installed version with your package manager.
- NuGet magick.net-q8-openmp-x64: check the installed version with your package manager.
- NuGet magick.net-q16-hdri-openmp-x64: check the installed version with your package manager.
- NuGet magick.net-q16-openmp-arm64: check the installed version with your package manager.
- NuGet magick.net-q16-x64: check the installed version with your package manager.
- NuGet magick.net-q8-x64: check the installed version with your package manager.
- NuGet magick.net-q8-openmp-arm64: check the installed version with your package manager.
- NuGet magick.net-q8-anycpu: check the installed version with your package manager.
- NuGet magick.net-q16-openmp-x86: check the installed version with your package manager.
- NuGet magick.net-q16-arm64: check the installed version with your package manager.
- NuGet magick.net-q16-hdri-x64: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on magick.net-q8-arm64, magick.net-q8-x86, magick.net-q16-hdri-anycpu, magick.net-q16-openmp-x64, magick.net-q16-anycpu, magick.net-q16-hdri-x86, magick.net-q16-hdri-openmp-arm64, magick.net-q16-hdri-arm64, magick.net-q16-x86, magick.net-q8-openmp-x64, magick.net-q16-hdri-openmp-x64, magick.net-q16-openmp-arm64, magick.net-q16-x64, magick.net-q8-x64, magick.net-q8-openmp-arm64, magick.net-q8-anycpu, magick.net-q16-openmp-x86, magick.net-q16-arm64, magick.net-q16-hdri-x64.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j96m-mjp6-99xr (GitHub-reviewed advisory GHSA-j96m-mjp6-99xr lists affected ranges: NuGet magick.net-q16-anycpu >=0 =0 =0 =0 =0 =0 =0 =0 =0 <=12.3.0; NuGet…)

Commands are suggestions: review each one before running it.