How many CVEs have patched DestroyPolicyElement?

1 published CVEs changed DestroyPolicyElement in ImageMagick/ImageMagick6, in 1 distinct patches totalling 44 changed lines, between 2026 and 2026.

What is the latest CVE that changed DestroyPolicyElement?

CVE-2026-105083 (ImageMagick before 7.1.2-32 and 6.9.13-57 Security Policy Bypass via policy.xml DOCTYPE), published 2026-10-03, changed lines 1056 to 1372 of magick/policy.c.

How does DestroyPolicyElement compare to the rest of ImageMagick/ImageMagick6?

ImageMagick/ImageMagick6 has 79 CVEs with a located fix in total; 1 of them changed DestroyPolicyElement.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

ImageMagick/ImageMagick6

Function

DestroyPolicyElement

Name: DestroyPolicyElement in ImageMagick/ImageMagick6: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

magick/policy.c

Last patched October 3, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

44

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

DestroyPolicyElement in ImageMagick/ImageMagick6 was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 44 lines in total.

ImageMagick/ImageMagick6 has 79 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed DestroyPolicyElement, newest first, with the lines each fix touched.

ImageMagick before 7.1.2-32 and 6.9.13-57 Security Policy Bypass via policy.xml DOCTYPE
CVE-2026-105083 · lines 1056–1372 · +22 −22 in 2 hunks
Low · CVSS 1.8
EPSS 0.1%2026-10-03

Get an alert when the next CVE fix lands in ImageMagick/ImageMagick6, with the patched functions.

Monitor ImageMagick6 CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in ImageMagick/ImageMagick6 changed by the most CVE fixes.

ReadTIFFImage5 CVEs · coders/tiff.c WritePNMImage3 CVEs · coders/pnm.c MogrifyImageList3 CVEs · wand/mogrify.c ReadImage2 CVEs · magick/constitute.c WritePDFImage2 CVEs · coders/pdf.c ReadCUTImage2 CVEs · coders/cut.c

All patched functions in ImageMagick/ImageMagick6

Frequently asked questions

Common questions about CVE fixes to DestroyPolicyElement.

How many CVEs have patched DestroyPolicyElement?: 1 published CVEs changed DestroyPolicyElement in ImageMagick/ImageMagick6, in 1 distinct patches totalling 44 changed lines, between 2026 and 2026.
What is the latest CVE that changed DestroyPolicyElement?: CVE-2026-105083 (ImageMagick before 7.1.2-32 and 6.9.13-57 Security Policy Bypass via policy.xml DOCTYPE), published 2026-10-03, changed lines 1056 to 1372 of magick/policy.c.
How does DestroyPolicyElement compare to the rest of ImageMagick/ImageMagick6?: ImageMagick/ImageMagick6 has 79 CVEs with a located fix in total; 1 of them changed DestroyPolicyElement.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track ImageMagick/ImageMagick6 CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing