CVE-2026-56371

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. 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: epss, nvd
Trending — 4 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: 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 and 6.9.13-40 contains a memory leak in coders/txt.c when processing TXT files with texture attributes: the texture object allocated via ReadImage is not released when GetTypeMetrics fails, leaking memory each time a crafted TXT file with a texture attribute is processed.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
17.0%
KEV
Not listed

Published

June 23, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

ImageMagick - Memory Leak in TXT File Processing via Texture Attribute | Advisories | VulnCheck

https://www.vulncheck.com/advisories/imagemagick-memory-leak-in-txt-file-processing-via-texture-attribute
github Patch Available🟡 PoC Available

Memory leak in coders/txt.c without freetype · Advisory · ImageMagick/ImageMagick · GitHub

https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-3q5f-gmjc-38r8

Vendor Advisories for CVE-2026-56371(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 26× in last 7d / 46× 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-07 06:56 UTCEG score recompute
  2. 2026-07-07 06:56 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 07:17 UTCEG score recompute
  6. 2026-07-06 07:16 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 07:34 UTCEG score recompute
  10. 2026-07-05 07:34 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 07:59 UTCEG score recompute
  14. 2026-07-04 07:59 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 08:25 UTCEG score recompute
  18. 2026-07-03 08:25 UTCGHSA enrichment
  19. 2026-07-02 16:57 UTCNVD updateCVSS v4 → 6.9
  20. 2026-07-02 08:49 UTCEG score recompute
  21. 2026-07-02 08:48 UTCGHSA enrichment
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-07-01 09:10 UTCEG score recompute
  24. 2026-07-01 09:10 UTCGHSA enrichment
  25. 2026-06-30 09:36 UTCEG score recompute
Show 21 more
  1. 2026-06-30 09:36 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 10:03 UTCEG score recompute
  5. 2026-06-29 10:03 UTCGHSA enrichment
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 10:29 UTCEG score recompute
  8. 2026-06-28 10:29 UTCGHSA enrichment
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-27 10:56 UTCEG score recompute
  12. 2026-06-27 10:56 UTCGHSA enrichment
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-26 11:23 UTCEG score recompute▲ 5.30
  15. 2026-06-26 11:23 UTCGHSA enrichment
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 16:02 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 14:00 UTCNVD update
  20. 2026-06-23 12:42 UTCEG score recompute
  21. 2026-06-23 12:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56371?
CVE-2026-56371 is a medium vulnerability published on June 23, 2026. ImageMagick before 7.1.2-15 and 6.9.13-40 contains a memory leak in coders/txt.c when processing TXT files with texture attributes: the texture object allocated via ReadImage is not released when GetTypeMetrics fails, leaking memory each time a crafted TXT file with a texture attribute is processed.
When was CVE-2026-56371 disclosed?
CVE-2026-56371 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56371 actively exploited?
CVE-2026-56371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56371?
CVE-2026-56371 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-56371?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56371, 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-56371

Explore →

Is Your Infrastructure Affected by CVE-2026-56371?

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

Start Free Scan →Browse All CVEs