CVE-2026-56368

HIGHNVD 7.53.7
EchelonGraph scoreLOW confidence

This low-severity CVE scores 3.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ImageMagick before 7.1.2-15 contains a memory leak vulnerability in multiple coders that write raw pixel data where allocated objects are not properly freed. Attackers can trigger this leak by processing specially crafted images, causing memory exhaustion and denial of service.

CVSS v3
7.5
EG Score
3.7(low)
EPSS
17.4%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github.
generic

ImageMagick - Memory Leak in Raw Pixel Data Coders | Advisories | VulnCheck

https://www.vulncheck.com/advisories/imagemagick-memory-leak-in-raw-pixel-data-coders
github Patch Available

Memory Leak in multiple coders that write raw pixel data · Advisory · ImageMagick/ImageMagick · GitHub

https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-wfx3-6g53-9fgc

Vendor Advisories for CVE-2026-56368(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 04:08 UTCOSV refresh
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 7 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-26 23:42 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 16:02 UTCNVD updateCVSS v4 → 6.3
  7. 2026-06-24 14:03 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56368?
CVE-2026-56368 is a high vulnerability published on February 25, 2026. ImageMagick before 7.1.2-15 contains a memory leak vulnerability in multiple coders that write raw pixel data where allocated objects are not properly freed. Attackers can trigger this leak by processing specially crafted images, causing memory exhaustion and denial of service.
When was CVE-2026-56368 disclosed?
CVE-2026-56368 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56368 actively exploited?
CVE-2026-56368 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56368?
CVE-2026-56368 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 3.7. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-56368?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56368, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56368

Explore →

Is Your Infrastructure Affected by CVE-2026-56368?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs