CVE-2026-47178

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% 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 — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.19.0 through 1.21.2, a crafted HEIF file (uncompressed unci codec, tiled, component-interleaved, 4:2:0) triggers a heap out-of-bounds write in libheif's uncompressed tile decoder. The write overwrites the C++ vtable pointer of an adjacent unc_decoder_component_interleave object; the next virtual call dispatches to an attacker-chosen address. Version 1.22.0 patches the issue.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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 computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 27, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Heap Out Of Bounds Write in unci subsystem · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-5x55-x5pf-9c6g

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibheif1 (1.21.2-3ubuntu0.2) @ resolute2026-08-30ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libheif1.11.0-1 ... 1.23.1-1 (39 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libheif1.15.1-1 ... 1.23.1-1 (33 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libheif1.19.8-11.19.8-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libheif1.19.8-1 ... 1.23.1-1 (9 versions)——

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 23× in last 7d / 106× 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.

Showing the most recent 100 of 129 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47178?
CVE-2026-47178 is a high vulnerability published on July 21, 2026. libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.19.0 through 1.21.2, a crafted HEIF file (uncompressed unci codec, tiled, component-interleaved, 4:2:0) triggers a heap out-of-bounds write in libheif's uncompressed tile decoder. The write overwrites the C++ vtable pointer…
When was CVE-2026-47178 disclosed?
CVE-2026-47178 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47178 actively exploited?
CVE-2026-47178 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47178?
CVE-2026-47178 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-47178?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47178, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47178?

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

Start Free Scan →Browse All CVEs