CVE-2026-47714

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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, secondary
Trending — 3 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

A fix is available — apply it.

libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, the inline mask parsing code in libheif/region.cc contains an integer overflow. Both width and height are unsigned int (32-bit) values parsed from the HEIF file. Their product can exceed UINT32_MAX, wrapping to a small value before the division by 8. This causes an undersized buffer allocation, leading to out-of-bounds memory access when the mask data is later interpreted as a width x height bitmap. Version 1.22.0 patches the issue.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 30, 2026

Advisory Details (1)

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

Integer overflow in inline mask size calculation causes undersized buffer allocation · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-h4wm-6wwf-qvhx

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibheif1 (1.17.6-1ubuntu4.6) @ noble2026-09-20ubuntu
ubuntulibheif1 (1.21.2-3ubuntu0.3) @ resolute2026-09-20ubuntu

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.2-1 (34 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.21.2-4 (8 versions)1.23.1-1—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 / 52× 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 133 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47714?
CVE-2026-47714 is a medium vulnerability published on July 21, 2026. libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, the inline mask parsing code in libheif/region.cc contains an integer overflow. Both width and height are unsigned int (32-bit) values parsed from the HEIF file. Their product can exceed UINT32_MAX, wrapping…
When was CVE-2026-47714 disclosed?
CVE-2026-47714 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47714 actively exploited?
CVE-2026-47714 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-47714?
CVE-2026-47714 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-47714?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47714, 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-47714

Explore →

Is Your Infrastructure Affected by CVE-2026-47714?

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

Start Free Scan →Browse All CVEs