dbcve.org
ImagemagickApplication

CVE-2026-22770

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 7.1.2-13 or later.
See remediation →
100/100
Remediation priority · Urgent
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. The BilateralBlurImage method will allocate a set of double buffers inside AcquireBilateralTLS. But, in versions prior to 7.1.2-13, the last element in the set is not properly initialized. This will result in a release of an invalid pointer inside DestroyBilateralTLS when the memory allocation fails. Version 7.1.2-13 contains a patch for the issue.

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 versions prior to 7.1.2-13 contain a double-free vulnerability in the BilateralBlurImage function. The AcquireBilateralTLS method fails to properly initialize the last element in a set of double buffers, causing an invalid pointer to be released in DestroyBilateralTLS when memory allocation fails.

MitigationUpgrade to ImageMagick version 7.1.2-13 or later to patch the initialization issue in AcquireBilateralTLS.

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:< 7.1.2-13

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. Determine installed ImageMagick version
    Run `identify -version` or `convert -version` on the system
    Affected if The version shown is earlier than 7.1.2-13 (e.g., 7.1.2-12, 7.1.2-0, 6.x.x)
  2. Locate BilateralBlur usage in image processing pipelines
    Search application logs, scripts, or source code for calls to BilateralBlur, -bilateral-filter, or the BilateralImage API function
    Affected if Any code or configuration invokes BilateralBlur functionality on images
  3. Inspect ImageMagick policy.xml for Bilateral module restrictions
    Check /etc/ImageMagick-6/policy.xml or the policy file returned by `identify -list policy` for <policy domain="coder" rights="none" pattern="BILATERAL"/>
    Affected if The Bilateral coder is not explicitly disabled and version is vulnerable
  4. Review image processing workflows for automated BilateralBlur invocation
    Examine any image processing workflows, batch scripts, or web applications that may call ImageMagick with bilateral blur operations
    Affected if Automated or user-driven workflows process images through BilateralBlur without version verification

The system is affected if ImageMagick version is below 7.1.2-13 AND BilateralBlur image processing is invoked in any workflow.

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 7.1.2-13 or later
Fixed in 7.1.2-13
Vendor patch github.com →
Interim mitigation

Upgrade to ImageMagick version 7.1.2-13 or later to patch the initialization issue in AcquireBilateralTLS.

Recommended fix High confidence

7.1.2-13

  1. 1. Check the current ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. Update your system's package repository to ensure you have access to the latest packages
  3. 3. Upgrade ImageMagick to version 7.1.2-13 or later using your system's package manager (e.g., 'apt-get update && apt-get upgrade imagemagick' for Debian/Ubuntu, or 'yum update ImageMagick' for RHEL/CentOS)
  4. 4. Verify the upgrade was successful by checking the new version with 'convert --version'

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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