LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24485: ImageMagick: Infinite loop vulnerability when parsing a PCD file

ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, when a PCD file does not contain a valid Sync marker, the DecodeImage() function becomes trapped in an infinite loop while searching for the Sync marker, causing the program to become unresponsive and continuously consume CPU resources, ultimately leading to system resource exhaustion and denial of service. Versions 7.1.2-15 and 6.9.13-40 contain a patch.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24485 can make ImageMagick hang when it processes a malformed PCD image. An attacker could cause services that accept or automatically process images to consume CPU and become unavailable. The issue is fixed in ImageMagick 7.1.2-15 and 6.9.13-40.

Executive priority

Prioritize remediation for internet-facing or customer-upload image processing. This is an availability risk, not a data theft issue, but it can disrupt dependent applications if image processing runs in shared service infrastructure.

Technical view

Before ImageMagick 7.1.2-15 and 6.9.13-40, DecodeImage() can enter an infinite loop while searching for a missing or invalid PCD Sync marker. The CVSS 3.1 score is 7.5, reflecting network-reachable, unauthenticated denial of service with high availability impact and no confidentiality or integrity impact.

Likely exposure

Highest exposure is in web applications, media pipelines, document converters, and background jobs that process user-supplied or untrusted images with ImageMagick, especially where PCD files are accepted or format detection is automatic.

Exploitation context

The source bundle does not show known active exploitation, and the CVE is not marked KEV. Exploitation requires causing a vulnerable ImageMagick instance to parse a crafted PCD file lacking a valid Sync marker, resulting in CPU exhaustion and denial of service.

Researcher notes

The public description attributes the bug to missing Sync marker handling in PCD parsing, causing DecodeImage() to loop indefinitely. The supplied commit is the relevant code change. Avoid assuming broader product impact beyond ImageMagick unless a vendor confirms bundled vulnerable versions.

Mitigation direction

  • Upgrade ImageMagick to 7.1.2-15 or 6.9.13-40 or later.
  • Check vendor guidance for packaged operating system or container updates.
  • Restrict or disable PCD processing where it is not required.
  • Apply resource limits to image-processing workers to reduce denial-of-service impact.
  • Review downstream wrappers or applications that bundle or invoke ImageMagick.

Validation and detection

  • Inventory ImageMagick versions on servers, containers, and build images.
  • Confirm production versions are 7.1.2-15, 6.9.13-40, or later.
  • Identify applications accepting untrusted image uploads or automated image conversion.
  • Check whether PCD input is enabled, accepted, or auto-detected.
  • Monitor image-processing services for sustained CPU spikes and worker hangs.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24485 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-24485Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ImageMagickImageMagick>= 7.0.0, < 7.1.2-15, < 6.9.13-40Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.