CVE-2026-32739

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% 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
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and below, a crafted 800-byte HEIF sequence file causes an infinite loop in Box_stts::get_sample_duration(), consuming 100% CPU indefinitely with zero progress, leading to DoS. The loop has no iteration limit or timeout and is triggered during file open (parsing) - before any user interaction or image decoding. The process stays alive (no crash, no error logged), making it invisible to crash-based monitoring. This issue has been fixed in version 1.22.0.

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

Published

May 19, 2026

Last Modified

July 24, 2026

Advisory Details (2)

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

Infinite Loop DoS in stts Sample Duration Lookup <=1.21.2 · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-j9g7-q9hv-gq8c
generic

Release v1.22.0 - generic image components, ISO/IEC 23001-17 (lossless images) rewrite · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/releases/tag/v1.22.0

Patch Availability(1)

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

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)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
libheif—1.23.0-r0—
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: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

(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 6× in last 7d / 32× 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 199 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-32739?
CVE-2026-32739 is a medium vulnerability published on May 19, 2026. libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and below, a crafted 800-byte HEIF sequence file causes an infinite loop in Boxstts::getsample_duration(), consuming 100% CPU indefinitely with zero progress, leading to DoS. The loop has no iteration limit or timeout…
When was CVE-2026-32739 disclosed?
CVE-2026-32739 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32739 actively exploited?
CVE-2026-32739 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 74.8% of all scored CVEs.
What is the CVSS score of CVE-2026-32739?
CVE-2026-32739 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-32739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32739, 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-32739

Explore →

Is Your Infrastructure Affected by CVE-2026-32739?

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

Start Free Scan →Browse All CVEs