dbcve.org
ImagemagickApplication

CVE-2026-49219

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 6.9.13-48 / 7.1.2-24 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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. Prior to versions 6.9.13-48 and 7.1.2-24, an incorrect parsing of the filename can result in a policy bypass and read files disallowed by a security policy using a symlink. This issue has been patched in versions 6.9.13-48 and 7.1.2-24.

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 6.9.13-48 and 7.1.2-24 contain a flaw in filename parsing that allows attackers to bypass security policies using symlinks, enabling unauthorized read access to files that should be restricted by the policy configuration.

MitigationUpgrade ImageMagick to version 6.9.13-48 or 7.1.2-24 or later, and audit existing security policies to ensure symlink-based bypasses are properly mitigated.

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-48>= 7.0.0-0, < 7.1.2-24

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check installed ImageMagick version
    Run `convert --version` (ImageMagick 6) or `magick --version` (ImageMagick 7) to retrieve the version number
    Affected if The installed version is less than 6.9.13-48, or is 7.0.0-0 through 7.1.2-23 (anything less than 7.1.2-24)
  2. Identify ImageMagick security policy file
    Locate the policy.xml file; common paths are /etc/ImageMagick-6/policy.xml, /etc/ImageMagick/policy.xml, or check the MAGICK_CONFIGURE_POLICY environment variable
    Affected if A security policy file exists and restricts file read access (such as by limiting https, http, mpeg, or other URI handlers, or restricting certain file patterns)
  3. Confirm policy-based restrictions are in use
    Inspect the policy.xml file and look for <policy> entries with rights="read" or rights="none" that restrict access to specific domains, protocols, or file patterns
    Affected if The security policy contains restrictions that rely on ImageMagick properly resolving symlinks before applying access controls
  4. Verify symlink resolution behavior
    Create a test symlink from a restricted path to an unrestricted file, then attempt to process it with ImageMagick using a policy-protected operation to see if the restriction is bypassed (or simply note that the vulnerability exists in the installed version)
    Affected if The installed version is in the affected range AND the environment relies on security policy to restrict file access

You are affected if your ImageMagick version is below 6.9.13-48 (for the 6.x branch) or below 7.1.2-24 (for the 7.x branch) AND you use ImageMagick security policies to restrict access to files or protocols that should not be reachable via symlink manipulation.

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-48 / 7.1.2-24 or later
Fixed in 6.9.13-487.1.2-24
Interim mitigation

Upgrade ImageMagick to version 6.9.13-48 or 7.1.2-24 or later, and audit existing security policies to ensure symlink-based bypasses are properly mitigated.

Recommended fix High confidence

6.9.13-48 (6.x branch) or 7.1.2-24 (7.x branch)

  1. 1. Identify your current ImageMagick version by running 'convert -version' or 'magick -version'
  2. 2. Determine which branch you are using (6.x or 7.x) from the version output
  3. 3. For systems using package managers: run 'apt-get update && apt-get install imagemagick' (Debian/Ubuntu) or 'yum update imagemagick' (RHEL/CentOS) or 'brew upgrade imagemagick' (macOS)
  4. 4. For source builds: download ImageMagick 6.9.13-48 (for 6.x branch) or 7.1.2-24 (for 7.x branch) from https://imagemagick.org/archive/
  5. 5. Verify the security patch is applied by checking 'convert -version' shows version 6.9.13-48 or later for 6.x, or 7.1.2-24 or later for 7.x
  6. 6. Test that ImageMagick functions correctly with your workflows
Caveat Point release upgrades typically preserve compatibility; however, 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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