MEDIUM 4.1

CVE-2026-46692: ImageMagick Distributed Cache Heap Buffer Overwrite Denial of Service

ImageMagick, a widely-used image manipulation tool, contains a heap buffer overwrite vulnerability in its distributed cache service. An attacker with local access to the cache service can trigger the flaw to crash the service, causing a denial of service. The vulnerability affects ImageMagick versions before 6.9.13-48 (legacy branch) and 7.1.2-23 (current branch). While the attack requires local connectivity to the cache daemon and elevated privileges, the impact is confined to availability—not confidentiality or integrity.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.1 MEDIUM · CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-122
Affected products
1 configuration(s)
Published / Modified
2026-06-10 / 2026-06-17

NVD description (verbatim)

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-23, an attacker who can connect to a magick -distribute-cache service can cause a heap buffer over-write in the server process. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability resides in ImageMagick's magick -distribute-cache service, a local inter-process communication component. A heap buffer overwrite occurs when the service processes specially crafted input from a connected client. The flaw is classified as CWE-122 (Heap-based Buffer Overflow). The CVSS 3.1 score of 4.1 (MEDIUM) reflects the requirement for local access (AV:L), high complexity to exploit (AC:H), high privilege level needed (PR:H), and impact limited to availability (A:H). No information disclosure or integrity compromise is possible through this vector.

Business impact

Organizations running ImageMagick's distributed cache service in multi-user environments face service interruptions if an authenticated local user or privileged attacker can reach the cache daemon. For production image processing pipelines relying on the cache service for performance, exploitation would degrade throughput and require service restart. The moderate CVSS score and operational friction (privilege and network prerequisites) mean this is not a critical remote exploit vector, but availability impact warrants timely patching in systems where uptime is essential.

Affected systems

ImageMagick versions 6.9.13-47 and earlier (6.x branch) and 7.1.2-22 and earlier (7.x branch) are vulnerable when the distributed cache service is enabled and accessible. Users running only the command-line tools without cache services, or those running patched versions 6.9.13-48 or 7.1.2-23 and later, are unaffected. Verify your installed version via `convert -version` and check whether the cache service is configured and running.

Exploitability

Exploitation requires: (1) local network or system access to reach the magick -distribute-cache listening socket, (2) ability to connect as an authenticated user or process, and (3) knowledge of the cache protocol to craft a malformed message triggering the buffer overwrite. The high complexity (AC:H) and privilege requirements (PR:H) limit opportunistic exploitation. There is no evidence of public exploit code or active in-the-wild attacks. This is not a remote code execution vector and does not enable privilege escalation.

Remediation

Upgrade ImageMagick to version 6.9.13-48 or later (6.x users) or 7.1.2-23 or later (7.x users). The patch directly addresses the heap buffer overflow in the cache service. Organizations should apply updates during standard maintenance windows and verify the service restarts cleanly. For systems where patching is delayed, restrict local access to the cache daemon socket via filesystem permissions or disable the distributed cache service if not essential.

Patch guidance

Download and install ImageMagick 6.9.13-48 (legacy) or 7.1.2-23 (current) from the official ImageMagick repository or your distribution's package manager. Verify the patch was applied by running `identify -version` or `convert -version` and confirming the version number matches or exceeds the patched release. Test image processing workflows post-update to ensure cache service functionality. Verify against the vendor advisory at imagemagick.org for distribution-specific instructions.

Detection guidance

Monitor for unusual termination or repeated restarts of the magick -distribute-cache daemon process, which may indicate exploitation attempts causing crashes. Check process logs for segmentation faults or core dumps involving the cache service. If available, enable cache service debug logging to detect malformed protocol messages. Network-level detection is difficult without traffic analysis, but unusual local connections to the cache socket may warrant investigation. Organizations should prioritize version scanning to identify vulnerable instances before exploitation occurs.

Why prioritize this

Although CVSS scores this MEDIUM (4.1), the practical risk is lower due to local-only attack surface and privilege requirements. Prioritize patching in multi-user systems or shared hosting environments where local users have network access to the cache daemon. Single-user or air-gapped systems running ImageMagick without the cache service enabled can defer updates, but should still plan for patching within 90 days. This is not an emergency-level vulnerability requiring immediate out-of-band action.

Risk score, explained

The CVSS 3.1 score of 4.1 reflects: AV:L (attack requires local presence, not remote), AC:H (high complexity due to buffer overwrite exploitation difficulty), PR:H (high privileges or authenticated access needed), and isolated impact on availability (A:H, but C:N and I:N). The score appropriately penalizes a vulnerability that requires significant preconditions but does cause service crashes. Organizations with strong local access controls and no exposed cache daemon may tolerate this risk longer; those with permissive local environments should prioritize patching sooner.

Frequently asked questions

Does this vulnerability allow remote code execution or remote access?

No. The attack requires local connectivity to the magick -distribute-cache socket and elevated user privileges or authentication. There is no remote network exploitation path. The impact is limited to denial of service (crashing the cache daemon), not code execution or lateral movement.

Do I need to patch if I don't use the distributed cache service?

If you run only the standard ImageMagick command-line tools (convert, identify, etc.) without explicitly enabling or configuring the distributed cache daemon, you are not affected. Verify by checking your system's process list or configuration files for magick -distribute-cache. If it is not running, patching is lower priority, but is still recommended as part of routine updates.

What is the difference between the 6.9.13-48 and 7.1.2-23 patches?

These are separate patch releases for two maintained branches of ImageMagick. Version 6.9.13-48 is the patched release for the legacy 6.x branch; version 7.1.2-23 is the patched release for the current 7.x branch. Both branches receive security fixes. Choose the branch your organization uses and upgrade to the corresponding patched version. Consult the vendor advisory for branch-specific guidance.

Can I work around this without patching?

Temporary mitigations include: (1) disabling the distributed cache service if not required for your workflow, (2) restricting filesystem permissions on the cache socket to trusted users only, and (3) isolating the system from untrusted local users. However, patching is the only permanent fix and should be applied within a reasonable maintenance window.

This analysis is provided for informational purposes and reflects publicly available information as of the publication date. No warranty is made regarding the accuracy, completeness, or timeliness of this content. Security teams should verify all patch version numbers, compatibility, and applicability against official vendor advisories and their own system configurations before deploying updates. CVE identifiers, CVSS scores, and severity ratings are derived from authoritative sources but may be subject to revision. This page does not constitute professional security advice; consult qualified security professionals for guidance specific to your environment. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).