dbcve.org
ImagemagickApplication

CVE-2025-57807

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-05
Fix available
A fix is available. Upgrade to 6.9.13-29 / 7.1.2-3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ImageMagick is free and open-source software used for editing and manipulating digital images. ImageMagick versions lower than 14.8.2 include insecure functions: SeekBlob(), which permits advancing the stream offset beyond the current end without increasing capacity, and WriteBlob(), which then expands by quantum + length (amortized) instead of offset + length, and copies to data + offset. When offset ≫ extent, the copy targets memory beyond the allocation, producing a deterministic heap write on 64-bit builds. No 2⁶⁴ arithmetic wrap, external delegates, or policy settings are required. This is fixed in version 14.8.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ImageMagick contains a heap buffer overflow vulnerability in the SeekBlob() and WriteBlob() functions. SeekBlob() allows advancing the stream offset beyond the current end without allocating additional memory, and WriteBlob() calculates buffer expansion using quantum + length rather than offset + length. When offset greatly exceeds extent, WriteBlob() copies data to a memory location beyond the allocated buffer, causing a deterministic heap write on 64-bit systems that can lead to arbitrary code execution.

MitigationUpgrade ImageMagick to version 14.8.2 or later. Given the critical CVSS score and deterministic heap exploitation nature, prioritize this upgrade in production environments immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ImagemagickApplication
Affected:< 6.9.13-29>= 7.0.0-0, < 7.1.2-3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if ImageMagick is installed
    Run `which convert` or `which magick` to locate the ImageMagick binary, or check package manager listings
    Affected if ImageMagick binary is found on the system
  2. Determine installed ImageMagick version
    Run `convert --version` or `magick --version` to display version information
    Affected if Version output is displayed and can be compared to affected ranges
  3. Compare version against affected ranges
    Parse the version number from the output and compare: for 6.x versions, check if < 6.9.13-29; for 7.x versions, check if >= 7.0.0-0 and < 7.1.2-3
    Affected if Installed version falls within < 6.9.13-29 or >= 7.0.0-0 but < 7.1.2-3
  4. Identify ImageMagick usage in custom applications
    Search application code and dependencies for ImageMagick library linking (e.g., grep for 'libMagick' or review package manifests)
    Affected if Custom applications link against a vulnerable ImageMagick library version

A system is affected if ImageMagick version 6.x below 6.9.13-29 or version 7.x from 7.0.0-0 up to but not including 7.1.2-3 is installed and actively used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.9.13-29 / 7.1.2-3 or later
Fixed in 6.9.13-297.1.2-3
Vendor patch github.com →
Interim mitigation

Upgrade ImageMagick to version 14.8.2 or later. Given the critical CVSS score and deterministic heap exploitation nature, prioritize this upgrade in production environments immediately.

Recommended fix High confidence

ImageMagick 7.1.2-3 or later (or 6.9.13-29 or later for the 6.x branch)

  1. Check your current ImageMagick version using 'convert -version' or 'identify -version'
  2. For Debian/Ubuntu: apt update && apt install imagemagick
  3. For RHEL/CentOS/Fedora: dnf update imagemagick or yum update imagemagick
  4. For Alpine: apk update && apk upgrade imagemagick
  5. For macOS (Homebrew): brew upgrade imagemagick
  6. For source compilation: Download ImageMagick 7.1.2-3 or later from https://imagemagick.org/archive/
  7. Verify the upgrade was successful by running 'convert -version' and confirming the version is 7.1.2-3 or later
Caveat ImageMagick upgrades may include changes to supported formats, delegate behaviors, or API; test critical image processing workflows after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Imagemagick Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-57807 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data