libheif is a HEIF and AVIF file format decoder and encoder. The fix for CVE-2026-3949 (commit b97c8b5, PR #1712) introduced an integer overflow in the very security check it added. The check itself can be bypassed, allowing a crafted HEIF file with a VVC track to trigger the same out-of-bounds heap read that CVE-2026-3949 was meant to prevent. This is a separate, currently-unpatched vulnerability. Issue #1712 was closed as fixed without testing the edge case where size is near UINT32_MAX. Version 1.22.0 patches the issue.
CVE-2026-47251
This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(medium)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity61% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 27, 2026
Advisory Details (2)
Auto-updated Jul 22, 2026Incomplete fix for CVE-2026-3949: integer overflow bypass in vvdec_push_data2 · Advisory · strukturag/libheif · GitHub
https://github.com/strukturag/libheif/security/advisories/GHSA-p6q9-fhf2-vj9vOut-of-Bounds Read in vvdec_push_data2() Due to Missing Length Validation · Issue #1712 · strukturag/libheif · GitHub
https://github.com/strukturag/libheif/issues/1712Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 14× 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.
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 15:23 UTCEG score recompute▼ 0.70
- 2026-07-27 15:21 UTCNVD updateCVSS v3 → 6.1
- 2026-07-27 09:33 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 09:58 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 22:56 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 23:11 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-125
- CVE-2010-3254EG 10.0HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2008-2663EG 10.0EPSS p90HIGH
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS p99CRITICAL
- CVE-2002-0639EG 9.8EPSS p97CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2009-2949EG 9.3EPSS p96HIGH
Frequently asked(5)
What is CVE-2026-47251?
When was CVE-2026-47251 disclosed?
Is CVE-2026-47251 actively exploited?
What is the CVSS score of CVE-2026-47251?
How do I remediate CVE-2026-47251?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-47251
Is Your Infrastructure Affected by CVE-2026-47251?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.