ImageMagick: Policy bypass through path traversal allows reading restricted content despite secured policy

Exploitation

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

CVSS

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

EPSS

• CVE-2026-25965: 0.75% estimated exploitation activity in the next 30 days; percentile 54.88 (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.

ImageMagick’s path security policy is enforced on the raw filename string before the filesystem resolves it. As a result, a policy rule such as /etc/ can be bypassed by a path traversal. The OS resolves the traversal and opens the sensitive file, but the policy matcher only sees the unnormalized path and therefore allows the read. This enables local file disclosure (LFI) even when policy-secure.xml is applied. Actions to prevent reading from files have been taken. But it make sure writing is also not possible the following should be added to your policy: And this will also be included in the project's more secure policies by default.

Published by the source

24 Feb 2026, 15:40 UTC

Last modified by the source

24 Feb 2026, 15:40 UTC

Source last checked

26 Oct 2026, 17:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8jvj-p28h-9gm7

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

# Patch Next advisory brief: CVE-2026-25965

Advisory: ImageMagick: Policy bypass through path traversal allows reading restricted content despite secured policy
IDs: CVE-2026-25965, GHSA-8jvj-p28h-9gm7
Record: https://patchnext.com/advisories/cve-2026-25965 (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: High (CVSS 8.6)
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 14.10.3; magick.net-q8-x86 14.10.3; magick.net-q16-hdri-anycpu 14.10.3; magick.net-q16-openmp-x64 14.10.3; magick.net-q16-anycpu 14.10.3; magick.net-q16-hdri-x86 14.10.3; magick.net-q16-hdri-openmp-arm64 14.10.3; magick.net-q16-hdri-arm64 14.10.3; magick.net-q16-x86 14.10.3; magick.net-q8-openmp-x64 14.10.3; magick.net-q16-hdri-openmp-x64 14.10.3; magick.net-q16-openmp-arm64 14.10.3; magick.net-q16-x64 14.10.3; magick.net-q8-x64 14.10.3; magick.net-q8-openmp-arm64 14.10.3; magick.net-q8-anycpu 14.10.3; magick.net-q16-openmp-x86 14.10.3; magick.net-q16-arm64 14.10.3; magick.net-q16-hdri-x64 14.10.3. A vendor fix does not mean a deployment is fixed.

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

## 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-8jvj-p28h-9gm7 (GitHub-reviewed advisory GHSA-8jvj-p28h-9gm7 lists affected ranges: NuGet magick.net-q16-anycpu >=0 =0 =0 =0 =0 =0 =0 =0 =0 <14.10.3; NuGet…)

Commands are suggestions: review each one before running it.