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:

<policy domain="path" rights="none" pattern="*../*"/>

And this will also be included in the project's more secure policies by default.

References

• GHSA-8jvj-p28h-9gm7
• https://nvd.nist.gov/vuln/detail/CVE-2026-25965
• https://github.com/dlemstra/Magick.NET/releases/tag/14.10.3