libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.2, crafted HEIF or AVIF mime metadata and unci image data can cause decompress_brotli() and do_inflate() to grow accumulated output without an effective size limit or MemoryHandle accounting. The brotli path has no output bound, while the zlib path checks only a small temporary buffer in a branch that valid streams do not reach, and overlapping icef units can decompress the same payload repeatedly. HeifContext::interpret_heif_file_images() processes multiple compressed metadata items during file opening, allowing a small file to consume unbounded memory and terminate the process. This issue is fixed in version 1.23.2.
CVE-2026-84384
HIGHPre-NVD 7.57.5Elevated
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (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: secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (3)
Auto-updated Sep 18, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
v1.23.2 - security release
Patch available: strukturag/libheif v1.23.2
https://github.com/strukturag/libheif/releases/tag/v1.23.2github_commit Patch Available
commit 21893e8f66c8 (strukturag/libheif)
Patch available: strukturag/libheif v1.23.2 (contains commit 21893e8f66c8)
https://github.com/strukturag/libheif/commit/21893e8f66c8b79363ca2809391b07d35e1a95ecgithub Patch Available🟡 PoC Available
Security report: brotli/zlib decompression paths lack output-size limits, allowing decompression-bomb OOM/DoS · Advisory · strukturag/libheif · GitHub
https://github.com/strukturag/libheif/security/advisories/GHSA-24wx-9w62-c96wWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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.
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:34 UTCEG score recompute
- 2026-09-18 16:25 UTCEG score recompute
- 2026-09-18 16:02 UTCEG score recompute
- 2026-09-18 15:59 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-84384?
CVE-2026-84384 is a high vulnerability published on September 18, 2026. libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.2, crafted HEIF or AVIF mime metadata and unci image data can cause decompressbrotli() and doinflate() to grow accumulated output without an effective size limit or MemoryHandle accounting. The brotli path has no…
When was CVE-2026-84384 disclosed?
CVE-2026-84384 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-84384?
CVE-2026-84384 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-84384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84384, 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-84384
Is Your Infrastructure Affected by CVE-2026-84384?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.