Security readout for executives and security teams
Plain-English summary
ImageMagick can crash when handling JBIG images because its decoder may use an uninitialized pointer. Systems that process images from users or external sources could suffer service outages. The available sources identify fixed ImageMagick releases but do not show confirmed active exploitation.
Executive priority
Prioritize remediation for internet-facing or customer-facing image-processing services. The primary business risk is service disruption, so patching should be scheduled promptly where untrusted images are accepted.
Technical view
Before ImageMagick 7.1.2-16 and 6.9.13-41, a missing check in the JBIG decoder can trigger an uninitialized pointer dereference. The CVSS 3.1 vector indicates network reachability, low complexity, no privileges, no user interaction, and availability impact only.
Likely exposure
Exposure is most likely in web applications, APIs, batch pipelines, CMS platforms, and security tooling that use vulnerable ImageMagick versions to process untrusted image files, especially JBIG content or formats routed through the JBIG decoder.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. The risk is denial of service rather than data theft or code execution based on the provided CVSS impacts.
Researcher notes
Track the JBIG decoder path and affected version ranges: >= 7.0.0, < 7.1.2-16 and < 6.9.13-41. Provided evidence supports availability impact only; exploit availability and product-specific downstream status require vendor advisories.
Mitigation direction
- Upgrade ImageMagick to 7.1.2-16, 6.9.13-41, or later.
- Apply distribution vendor updates, including Red Hat advisories where applicable.
- Confirm packaged builds include the relevant backported fix.
- Reduce processing of untrusted JBIG images until patched, where feasible.
- Check vendor guidance before relying on compensating controls.
Validation and detection
- Inventory ImageMagick versions across hosts, containers, and application dependencies.
- Identify services that process externally supplied images with ImageMagick.
- Verify upgraded packages report fixed or vendor-backported versions.
- Review vendor advisories for product-specific applicability and errata status.
- Monitor crash logs for image-processing denial-of-service symptoms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-252: 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 lookupCWE-824: 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 lookupCVE-2026-28691 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-09T22:02:36.659Z: Reported to Red Hat.
- 2026-03-09T21:40:42.117Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-wj8w-pjxf-9g4fCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-28691CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2445902CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-28691.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:6713CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unchecked Return Value
Unchecked Return Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Access of Uninitialized Pointer
Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.