CVE-2026-130670
Description
A flaw was found in ImageMagick. This vulnerability allows an attacker to cause an information disclosure or a denial of service (DoS) by convincing a user or system to process crafted BGRO image data. Due to a heap buffer over-read, where data is read beyond allocated memory boundaries, processing the malformed image can leak adjacent memory contents or crash the application.
Statement
This vulnerability is rated with a Low severity because it requires an attacker to convince a user or automated pipeline to parse an untrusted BGRO file, and the impact is confined to an out-of-bounds heap read that at most yields adjacent memory disclosure or process termination. In Red Hat Enterprise Linux deployments, ImageMagick operates primarily as an on-demand utility or backend parser rather than a persistently listening network service, restricting exposure to scenarios where untrusted graphics are ingested. The flaw does not permit code execution or persistent compromise of system integrity.
Mitigation
Prevent ImageMagick from processing BGRO format images by disabling the coder in the security policy configuration.
Edit `/etc/ImageMagick-6/policy.xml` (or `/etc/ImageMagick-7/policy.xml` depending on the installed version) and add the following entry inside the `<policymap>` block:
xml
<policy domain="coder" rights="none" pattern="BGRO" />
Caveats:
Disabling the BGRO coder prevents ImageMagick from reading or writing BGRO image files, which will impact workflows reliant on this specific format. If ImageMagick is invoked by background application services or long-running worker processes, restart those services to ensure the modified policy configuration takes effect. Furthermore, isolate processes handling untrusted media within a sandboxed or containerized environment.
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.3 | N/A | 3.3 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.