CVE-2026-50142

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.0, a crafted HEIF sequence accepted by heif_context_read_from_memory() with the msf1 sequence brand can cause unbounded heap allocation. In libheif/sequences/seq_boxes.cc, Box_stsz::parse() applies max_sequence_frames only to variable-size samples, so fixed-size mode accepts an attacker-controlled sample_count without a bound. In libheif/sequences/track.cc, Track::load() also adds current_sample_idx and samples_per_chunk in 32-bit arithmetic, allowing the consistency check to be bypassed by wraparound. The resulting values reach the Chunk::Chunk() allocation path, which can consume gigabytes of memory and crash or stall the process through memory exhaustion. This issue is fixed in version 1.23.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 19, 2026

Advisory Details (3)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github Patch Available🟡 PoC Available

libheif: unbounded heap allocation in HEIF sequence parser (stsz fixed-size mode missing bound check) · Advisory · strukturag/libheif · GitHub

https://github.com/strukturag/libheif/security/advisories/GHSA-jvmp-j3cw-84mh
github_release Patch Available

v1.23.0

Patch available: strukturag/libheif v1.23.0

https://github.com/strukturag/libheif/releases/tag/v1.23.0
github_commit Patch Available

commit a6caa38f7a70 (strukturag/libheif)

Patch available: strukturag/libheif v1.23.0 (contains commit a6caa38f7a70)

https://github.com/strukturag/libheif/commit/a6caa38f7a70d66dc9caec2a7bfe20935b32c622

Patch Availability(1)

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

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.

Weakness Classification(2)

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 25× in last 7d / 51× 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.

  1. 2026-08-31 00:12 UTCEG score recompute
  2. 2026-08-31 00:12 UTCVendor advisory
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 12:59 UTCVendor advisory
  5. 2026-08-30 01:46 UTCEG score recompute
  6. 2026-08-30 01:46 UTCVendor advisory
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-29 02:43 UTCEG score recompute
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 19:14 UTCEG score recompute
  11. 2026-08-27 19:14 UTCVendor advisory
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-27 07:25 UTCVendor advisory
  14. 2026-08-26 20:11 UTCEG score recompute
  15. 2026-08-26 20:11 UTCVendor advisory
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-26 08:56 UTCVendor advisory
  18. 2026-08-25 21:42 UTCEG score recompute
  19. 2026-08-25 21:42 UTCVendor advisory
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 10:06 UTCVendor advisory
  22. 2026-08-24 22:51 UTCEG score recompute
  23. 2026-08-24 22:51 UTCVendor advisory
  24. 2026-08-24 11:38 UTCEG score recompute
  25. 2026-08-24 11:38 UTCVendor advisory
Show 26 more
  1. 2026-08-24 00:24 UTCVendor advisory
  2. 2026-08-23 13:10 UTCVendor advisory
  3. 2026-08-23 01:56 UTCEG score recompute
  4. 2026-08-23 01:56 UTCVendor advisory
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 14:43 UTCVendor advisory
  7. 2026-08-22 03:29 UTCEG score recompute
  8. 2026-08-22 03:29 UTCVendor advisory
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 16:15 UTCVendor advisory
  11. 2026-08-21 05:01 UTCEG score recompute
  12. 2026-08-21 05:01 UTCVendor advisory
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 17:47 UTCVendor advisory
  15. 2026-08-20 06:34 UTCVendor advisory
  16. 2026-08-19 19:20 UTCEG score recompute
  17. 2026-08-19 19:20 UTCVendor advisory
  18. 2026-08-19 18:58 UTCEG score recompute
  19. 2026-08-19 18:58 UTCVendor advisory
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 09:37 UTCVendor advisory
  22. 2026-08-18 22:23 UTCEG score recompute
  23. 2026-08-18 22:23 UTCVendor advisory
  24. 2026-08-18 21:23 UTCEG score recompute
  25. 2026-08-18 21:23 UTCVendor advisory
  26. 2026-08-18 21:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50142?
CVE-2026-50142 is a high vulnerability published on August 18, 2026. libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.0, a crafted HEIF sequence accepted by heifcontextreadfrommemory() with the msf1 sequence brand can cause unbounded heap allocation. In libheif/sequences/seqboxes.cc, Boxstsz::parse() applies maxsequenceframes only…
When was CVE-2026-50142 disclosed?
CVE-2026-50142 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50142 actively exploited?
CVE-2026-50142 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.9% of all scored CVEs.
What is the CVSS score of CVE-2026-50142?
CVE-2026-50142 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50142?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50142, 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

Explore the affected products and dependency analysis for CVE-2026-50142

Explore →

Is Your Infrastructure Affected by CVE-2026-50142?

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

Start Free Scan →Browse All CVEs