CVE-2026-84384

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-83022 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
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.2
GitHub commit Patch Available

commit 21893e8f66c8 (strukturag/libheif)

Patch available: strukturag/libheif v1.23.2 (contains commit 21893e8f66c8)

https://github.com/strukturag/libheif/commit/21893e8f66c8b79363ca2809391b07d35e1a95ec
GitHub advisoryMentions a patch (unverified)

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-c96w

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibheif1 (1.1.0-2ubuntu0.1~esm5) @ bionic2026-10-28ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libheif1.15.1-1 ... 1.23.4-1~deb13u1 (37 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libheif1.19.8-1 ... 1.23.3-1 (12 versions)
  • every version up to 1.23.4-1~deb13u1: fixed in 1.23.4-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libheif1.19.8-1 ... 1.23.1-1 (9 versions)
  • every version up to 1.23.2-1: fixed in 1.23.2-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 61× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-28 07:49 UTCEG score recompute
  7. 2026-10-28 07:49 UTCVendor advisory
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-25 13:56 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-20 18:01 UTCEG score recompute
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-18 03:06 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 73 more
  1. 2026-10-13 05:36 UTCEG score recompute
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-12 14:53 UTCEG score recompute
  4. 2026-10-12 04:57 UTCVendor advisory
  5. 2026-10-11 19:18 UTCEG score recompute
  6. 2026-10-11 16:35 UTCEG score recompute
  7. 2026-10-11 15:14 UTCVendor advisory
  8. 2026-10-11 13:52 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-11 02:48 UTCEG score recompute
  11. 2026-10-11 02:48 UTCVendor advisory
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-10 14:19 UTCVendor advisory
  14. 2026-10-10 01:50 UTCEG score recompute
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-09 00:57 UTCEG score recompute
  17. 2026-10-09 00:57 UTCVendor advisory
  18. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-08 12:31 UTCVendor advisory
  20. 2026-10-08 00:05 UTCEG score recompute
  21. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-07 11:38 UTCVendor advisory
  23. 2026-10-06 23:08 UTCEG score recompute
  24. 2026-10-06 23:08 UTCVendor advisory
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  26. 2026-10-06 10:42 UTCVendor advisory
  27. 2026-10-05 22:06 UTCEG score recompute
  28. 2026-10-05 22:06 UTCVendor advisory
  29. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-10-05 09:40 UTCEG score recompute
  31. 2026-10-05 09:40 UTCVendor advisory
  32. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  33. 2026-10-04 21:13 UTCVendor advisory
  34. 2026-10-03 20:21 UTCEG score recompute
  35. 2026-10-03 20:21 UTCVendor advisory
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-10-02 19:17 UTCEG score recompute
  38. 2026-10-02 19:17 UTCVendor advisory
  39. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-10-02 06:51 UTCEG score recompute
  41. 2026-10-02 06:51 UTCVendor advisory
  42. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-10-01 18:25 UTCVendor advisory
  44. 2026-10-01 05:35 UTCVendor advisory
  45. 2026-09-30 17:09 UTCEG score recompute
  46. 2026-09-30 17:09 UTCVendor advisory
  47. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  48. 2026-09-30 04:43 UTCVendor advisory
  49. 2026-09-29 16:08 UTCEG score recompute
  50. 2026-09-29 03:41 UTCEG score recompute
  51. 2026-09-28 15:13 UTCEG score recompute
  52. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  53. 2026-09-27 14:20 UTCEG score recompute
  54. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  55. 2026-09-27 01:54 UTCEG score recompute
  56. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  57. 2026-09-26 00:58 UTCEG score recompute
  58. 2026-09-25 00:02 UTCEG score recompute
  59. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  60. 2026-09-23 23:09 UTCEG score recompute
  61. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  62. 2026-09-22 22:02 UTCEG score recompute
  63. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  64. 2026-09-21 21:09 UTCEG score recompute
  65. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  66. 2026-09-21 08:43 UTCEG score recompute
  67. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  68. 2026-09-19 19:19 UTCEG score recompute
  69. 2026-09-18 18:27 UTCEG score recompute
  70. 2026-09-18 17:34 UTCEG score recompute
  71. 2026-09-18 16:25 UTCEG score recompute
  72. 2026-09-18 16:02 UTCEG score recomputeFirst assessed: 7.5 HIGH
  73. 2026-09-18 15:59 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-84384?
CVE-2026-84384 is a high-severity vulnerability; its CVE record was 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 decompress_brotli() and do_inflate() to grow accumulated output without an effective size limit or MemoryHandle accounting. The brotli path has no…
When was the CVE record for CVE-2026-84384 published?
The CVE record for CVE-2026-84384 was published on September 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-84384 actively exploited?
CVE-2026-84384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84384?
CVE-2026-84384 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84384?
A fix for CVE-2026-84384 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84384

Explore →

Is Your Infrastructure Affected by CVE-2026-84384?

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

Book a Demo →Browse All CVEs