cve.bz

CVE-2025-68469 imagemagick imagemagick: Heap-based Buffer Overflow

2.0 lowExploit referenceEPSS 0.2%Fix available

Low (2.0) in imagemagick imagemagick. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in Magick.NET-Q16-AnyCPU 13.2.0.

On this page
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.1-14, ImageMagick crashes when processing a crafted TIFF file. Version 7.1.1-14 fixes the issue.

Severity

CVSS 4.0

2.0 low
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-12-18. 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-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-68469 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68469?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68469?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-2025-68469 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-2025-68469

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-2025-68469](https://cve.bz/cve/badge/CVE-2025-68469.svg)](https://cve.bz/cve/CVE-2025-68469)

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
imagemagick:imagemagickbefore 7.1.1-14

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-AnyCPU<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-HDRI-AnyCPU<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-HDRI-OpenMP-arm64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-HDRI-OpenMP-x64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-HDRI-arm64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-HDRI-x64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-HDRI-x86<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-OpenMP-arm64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-OpenMP-x64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-arm64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-x64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q16-x86<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q8-AnyCPU<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q8-OpenMP-arm64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q8-OpenMP-x64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q8-arm64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q8-x64<13.2.013.2.0
GHSA-fff3-4rp7-px97NuGetMagick.NET-Q8-x86<13.2.013.2.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11imagemagick8:6.9.11.60+dfsg-1.3+deb11u8DLA-4429-1
Debian12imagemagick8:6.9.11.60+dfsg-1.6+deb12u5DEBIAN-CVE-2025-68469
Debian13, 14imagemagick8:6.9.12.98+dfsg1-2DEBIAN-CVE-2025-68469
Ubuntu25.10, 26.10, Pro:14.04:LTS and 6 moreimagemagickno fix listedUBUNTU-CVE-2025-68469
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 moreImageMagick7.1.0.9-150400.6.58.1SUSE-SU-2026:0013-1
SUSELinux Enterprise Server LTSS Extended Security 12 SP5ImageMagick6.8.8.1-71.221.1SUSE-SU-2026:0059-1
Alpinev3.22, v3.23, v3.24imagemagick7.1.2.12-r0ALPINE-CVE-2025-68469

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; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpine.

Red Hat

Red Hat rates this Low.

Red Hat's statement

To exploit this issue, an attacker needs to convince a user to process a crafted TIFF file with ImageMagick. Additionally, this vulnerability can cause a heap-based buffer overflow, but there is no evidence of memory corruption or code execution, limiting the impact to an application crash. Due to these reasons, this flaw has been rated with a low severity.

Red Hat's mitigation

To mitigate this issue, avoid processing untrusted TIFF files with ImageMagick. In environments where ImageMagick processes files automatically, ensure that all input files originate from trusted sources or implement strict input validation to prevent the processing of malicious TIFF files.

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

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-2025-68469.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON