dbcve.org
ImagemagickApplication

CVE-2026-61858

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-11
Fix available
A fix is available. Upgrade to 6.9.13-51 / 7.1.2-26 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.

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 before 7.1.2-26 has a policy bypass vulnerability in its APNG encoder and external delegate handling. The encoder lacks proper validation checks that enforce the configured security policies, allowing attackers to write files to paths that should be restricted by those policies. This bypass occurs specifically during the APNG encoding process where policy restrictions are not correctly applied.

MitigationUpgrade ImageMagick to version 7.1.2-26 or later which contains the proper validation checks. Additionally, review and restrict external delegate configurations in policy.xml to minimize the attack surface until the upgrade is applied.

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-51>= 7.0.0-0, < 7.1.2-26

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
None
Integrity
Low
Availability
None

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

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. Determine installed ImageMagick version
    Run 'convert --version' or 'magick --version' on the command line to retrieve the installed version number
    Affected if The version shown is less than 6.9.13-51, or is 7.0.0-0 through 7.1.2-25 (including any 7.0.x or 7.1.x variants before 7.1.2-26)
  2. Verify APNG format support is enabled
    Run 'convert -list format' and look for APNG in the output, or attempt a simple APNG read/write operation with 'convert input.png output.apng' to confirm APNG encoding capability exists
    Affected if APNG format support is listed as Read/Write or enabled in the format list
  3. Locate and inspect the security policy configuration file
    Find policy.xml in /etc/ImageMagick-6/, /etc/ImageMagick-7/, or /etc/ImageMagick/ (path varies by installation), then examine its contents for any path or file-related restrictions
    Affected if A policy.xml file exists and contains <policy> entries that restrict file write operations or specific directory paths (the bypass allows writing beyond these restrictions)
  4. Test whether APNG encoding can write to a restricted location
    If policy.xml restricts certain paths (such as '/*' or specific directories), attempt to encode an image to APNG format and write to a path that should be blocked by policy (e.g., a path outside allowed directories)
    Affected if The APNG encoder successfully writes a file to a location that the policy.xml should have denied

You are affected if your ImageMagick version is in the vulnerable range (below 6.9.13-51 or between 7.0.0-0 and 7.1.2-25) AND you have APNG encoding enabled AND your security policies are configured to restrict file writes that the APNG encoder can now bypass.

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-51 / 7.1.2-26 or later
Fixed in 6.9.13-517.1.2-26
Interim mitigation

Upgrade ImageMagick to version 7.1.2-26 or later which contains the proper validation checks. Additionally, review and restrict external delegate configurations in policy.xml to minimize the attack surface until the upgrade is applied.

Recommended fix Moderate confidence

7.1.2-26 (or 6.9.13-51 for the 6.x branch)

  1. Identify the current ImageMagick version using 'convert --version' or 'magick --version'
  2. If using the 7.x branch, upgrade to version 7.1.2-26 or later using your system's package manager (e.g., 'apt-get install imagemagick', 'yum update ImageMagick', or 'brew upgrade imagemagick')
  3. If using the 6.x branch, upgrade to version 6.9.13-51 or later
  4. Verify the upgrade was successful by running 'convert --version' or 'magick --version' and confirming the version number meets the fixed release criteria
Caveat ImageMagick minor version upgrades may include behavioral changes in image processing; test critical workflows after upgrade

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61858 — 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-2026-61858 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