Skip to main content
Mallory
HighVulnerability

CVE-2026-25794: Heap buffer overflow in ImageMagick WriteUHDRImage

Published Feb 24, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v3.1
EPSS0.46%40th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Imagemagick
IdentifiersCVE-2026-25794CWE-190 · Integer Overflow or Wraparound

CVE-2026-25794 is an integer-overflow-driven heap memory corruption vulnerability in ImageMagick affecting versions prior to 7.1.2-15. The flaw is in the WriteUHDRImage routine in coders/uhdr.c, where 32-bit int arithmetic is used to calculate the size of a pixel buffer during UHDR image writing. For sufficiently large image dimensions, the multiplication overflows, producing a smaller-than-required allocation size. Subsequent writes then exceed the allocated heap buffer, resulting in an out-of-bounds heap write. The issue can cause process termination and may be exploitable for broader memory corruption effects depending on runtime conditions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can trigger a denial of service through process crash and may permit heap memory corruption via out-of-bounds write. Depending on allocator behavior, surrounding memory layout, and exploitability of the corrupted state, this may create conditions for further compromise beyond a crash, although the available information specifically confirms crash potential and heap overwrite.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, avoid processing or generating UHDR images from untrusted sources, and enforce strict upper bounds on accepted image dimensions and total pixel counts before invoking the affected write path. Running image-processing workloads in a sandboxed or isolated environment with least privilege can reduce the impact of a successful heap overwrite.

Remediation

Patch, then assume compromise.

Upgrade ImageMagick to version 7.1.2-15 or later, which contains the vendor patch for this issue. If ImageMagick is consumed through downstream wrappers or bindings, deploy the corresponding fixed package versions that incorporate the patched ImageMagick release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ImagemagickImagemagickapplication
FAQ

Frequently asked questions

Is CVE-2026-25794 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-25794 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25794?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-25794.
Is there a patch for CVE-2026-25794?
Upgrade ImageMagick to version 7.1.2-15 or later, which contains the vendor patch for this issue. If ImageMagick is consumed through downstream wrappers or bindings, deploy the corresponding fixed package versions that incorporate the patched ImageMagick release.
What products are affected by CVE-2026-25794?
Imagemagick.
How severe is CVE-2026-25794?
CVE-2026-25794 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 0.46% (40th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.