CVE-2026-93587

Description

A flaw was found in ImageMagick. A local user, by supplying a specific command line option to the PCD, CUBE, or HALD image decoders, can bypass configured resource limits. This policy bypass allows for extra memory allocation, enabling the user to exceed the intended memory policy limit. The most significant consequence is a denial of service (DoS) due to uncontrolled resource consumption.

Mitigation

To mitigate the potential for denial of service, system administrators can enforce resource limits for users who execute ImageMagick. This can be achieved by setting appropriate `ulimit` values for memory consumption (e.g., `as` for virtual memory or `rss` for resident set size) in user login scripts or system-wide configuration files like `/etc/security/limits.conf`. For example, to limit virtual memory for a user, add a line such as `username hard as 1048576` (1GB) to `/etc/security/limits.conf`. Changes to `/etc/security/limits.conf` require users to log out and back in to take effect and may impact other applications run by the user.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score3.3N/A3.3
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactLowN/ALow

Vector

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

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.