CVE-2026-130665
Description
A flaw was found in ImageMagick. A remote attacker could exploit this vulnerability by providing a crafted OpenEXR (EXR) image file for processing under low-memory conditions. When a specific memory allocation fails within the EXR decoder, a use-after-free condition occurs. This flaw primarily allows an attacker to cause an application crash, resulting in a denial of service (DoS), or potentially lead to memory corruption.
Statement
This vulnerability is rated as Low severity because successful exploitation requires precise conditions—specifically inducing an allocation failure under severe memory pressure—to cause an application crash or process termination. ImageMagick is generally executed as a short-lived command-line tool or isolated image conversion worker rather than a persistent privileged daemon, constraining the blast radius. As a result, the primary impact is localized denial of service during image processing without broader compromise of system integrity or confidentiality.
Mitigation
Disable the EXR coder in the ImageMagick security policy to prevent processing of EXR files:
1. Edit the ImageMagick security policy configuration file (e.g., `/etc/ImageMagick-6/policy.xml`) and insert the following rule inside the `<policymap>` section:
<policy domain="coder" rights="none" pattern="EXR" />
2. If ImageMagick is invoked by persistent services or application daemons (such as httpd or php-fpm), restart the associated services to apply the policy:
systemctl restart httpd
Caveat: This change prevents ImageMagick from reading or writing EXR format images, which will affect workflows dependent on EXR processing.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.7 | N/A | 3.7 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.