CVE-2026-130653

Description

A flaw was found in ImageMagick. A missing security policy check when decoding Magick Persistent Cache (MPC) image files allows an attacker to bypass file access restrictions. By supplying a specially crafted MPC file that references restricted file paths, an attacker can read sensitive files that should otherwise be blocked by the configured security policy.

Statement

This vulnerability is rated as having a Low severity because it requires local access or existing privileges to supply untrusted files to an application enforcing ImageMagick security policies, and any resulting impact is restricted strictly to unauthorized read operations without affecting system integrity or service availability. In standard Red Hat Enterprise Linux deployments, the Magick Persistent Cache format is primarily utilized as an internal caching mechanism rather than an externally exposed ingestion format. Consequently, exposure is limited to environments where arbitrary MPC files from unprivileged users are explicitly parsed by services relying on path-based access restrictions.

Mitigation

Disable the MPC coder within the ImageMagick security policy configuration.

Edit the ImageMagick policy configuration file (typically `/etc/ImageMagick-6/policy.xml` or `/etc/ImageMagick-7/policy.xml`) and add the following entry inside the `<policymap>` block:

xml
<policy domain="coder" rights="none" pattern="MPC" />

Caveats:
Disabling the MPC coder prevents ImageMagick from reading or writing images in the Magick Persistent Cache format. Any applications or workflows that rely on MPC files will fail to process them. If ImageMagick is invoked by persistent system services or web daemons, restart those services for the policy change to take effect.

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
ConfidentialityLowN/ALow
Integrity ImpactNoneN/ANone
Availability ImpactNoneN/ANone

Vector

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

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

Understanding the Weakness (CWE)

Integrity,Confidentiality

Technical Impact: Read Files or Directories

The application can operate on unexpected files, such as system files or configuration files. Confidentiality is violated when the targeted filename is not directly readable by the attacker.

Integrity,Confidentiality,Availability

Technical Impact: Modify Files or Directories; Execute Unauthorized Code or Commands

The application can operate on unexpected files. This may violate integrity if the filename is written to, or if the filename is for a program or other form of executable code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Other)

The application can operate on unexpected files. Availability can be violated if the attacker specifies an unexpected file that the application modifies. Availability can also be affected if the attacker specifies a filename for a large file, or points to a special device or a file that does not have the format that the application expects.

Frequently Asked Questions

Want to get errata notifications? Sign up here.