CVE-2026-41071

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% 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
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.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, a crafted HEIF sequence file where the saiz box declares more samples than actually exist in the track's chunk table causes a heap-buffer-overflow (out-of-bounds read) in the SampleAuxInfoReader constructor. The SampleAuxInfoReader constructor iterates over saiz->get_num_samples() samples but doesn't validate that this count is consistent with the number of chunks in the chunks vector. When saiz declares more samples than the chunks cover, the loop increments current_chunk past chunks.size(), causing an out-of-bounds read on the chunks vector. The vulnerability is triggered during file parsing (heif_context_read_from_file) without any additional user interaction. Any application using libheif to open untrusted HEIF files is affected. This issue has been fixed in version 1.22.0.

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

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jun 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Heap buffer over-read in SampleAuxInfoReader via crafted HEIF sequence file with mismatched saiz sample count · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-xj92-xjff-h8w3
github_release Patch Available

v1.22.0 - generic image components, ISO/IEC 23001-17 (lossless images) rewrite

Patch available: strukturag/libheif v1.22.0

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibheif1 (1.12.0-2ubuntu0.1~esm3) @ jammy2026-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

(3 across 3 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: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 / 28× 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 194 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41071?
CVE-2026-41071 is a high vulnerability published on May 22, 2026. libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, a crafted HEIF sequence file where the saiz box declares more samples than actually exist in the track's chunk table causes a heap-buffer-overflow (out-of-bounds read) in the SampleAuxInfoReader constructor.…
When was CVE-2026-41071 disclosed?
CVE-2026-41071 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41071 actively exploited?
CVE-2026-41071 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 76.9% of all scored CVEs.
What is the CVSS score of CVE-2026-41071?
CVE-2026-41071 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-41071?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41071, 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-41071

Explore →

Is Your Infrastructure Affected by CVE-2026-41071?

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

Start Free Scan →Browse All CVEs