cve.bz

CVE-2026-116151 imagemagick imagemagick

6.3 mediumEPSS 0.3%

Medium (6.3) in imagemagick imagemagick. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 contains a memory leak in the JNG encoder that fails to release allocated memory when processing a crafted image. Attackers can supply crafted images that are encoded to JNG to leak memory, potentially causing resource exhaustion and a limited denial of service.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-401 Missing Release of Memory after Effective Lifetime
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-116151 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116151?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116151?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116151 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-116151

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-116151](https://cve.bz/cve/badge/CVE-2026-116151.svg)](https://cve.bz/cve/CVE-2026-116151)

HTML:

<a href="https://cve.bz/cve/CVE-2026-116151"><img src="https://cve.bz/cve/badge/CVE-2026-116151.svg" alt="CVE-2026-116151"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ImageMagickfrom 7.0.0-0 before 7.1.2-33
ImageMagickbefore 6.9.13-58

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12imagemagick8:6.9.11.60+dfsg-1.6+deb12u15DEBIAN-CVE-2026-116151
Debian13imagemagick8:7.1.1.43+dfsg1-1+deb13u14DEBIAN-CVE-2026-116151
Debian14imagemagick8:7.1.2.33+dfsg1-1DEBIAN-CVE-2026-116151
Ubuntu26.10, Pro:14.04:LTS, Pro:16.04:LTS and 5 moreimagemagickno fix listedUBUNTU-CVE-2026-116151
openSUSETumbleweedImageMagick7.1.2.34-3.1openSUSE-SU-2026:12356-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This vulnerability is rated as Low severity because triggering the memory leak requires encoding files into the uncommon JNG format, and the blast radius is restricted to minor resource consumption without affecting system integrity or confidentiality. In typical Red Hat Enterprise Linux environments, ImageMagick runs primarily as a short-lived command-line utility where process termination automatically frees allocated memory, limiting the impact of memory leaks. Sustained resource exhaustion would only occur in long-running services or batch conversion pipelines that repeatedly process untrusted input directed to the JNG encoder.

Red Hat's mitigation

Disable the JNG coder in the ImageMagick security policy configuration.

To prevent the JNG encoder from being invoked, edit the ImageMagick policy configuration file (such as `/etc/ImageMagick-6/policy.xml` or `/etc/ImageMagick-7/policy.xml`, depending on the installed distribution) and insert the following line within the `<policymap>` element:

```xml

<policy domain="coder" rights="none" pattern="JNG" />

```

Caveats:

Disabling the JNG coder will prevent ImageMagick from reading or generating JNG files. Any workflows or applications relying specifically on JNG conversion will fail.

Warning:

If ImageMagick is used by persistent background processes or web application daemons, those services must be restarted for the policy changes to take effect.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6ImageMagickOut of support scope
Red Hat Enterprise Linux 7ImageMagickFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116151.

References

Check your stackJSON