CVE-2026-41069: libheif allows Out-of-bounds vector access leading to invalid dereference (DoS)
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: libheif (Debian:14) 1.23.1-1; libheif (openSUSE:Leap 16.0) 1.23.0-160000.1.1; libheif (openSUSE:Tumbleweed) 1.22.2-1.1.
Low priority for now. Upgrade to libheif (Debian:14) 1.23.1-1; libheif (openSUSE:Leap 16.0) 1.23.0-160000.1.1; libheif (openSUSE:Tumbleweed) 1.22.2-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, a malformed HEIF sequence file can trigger an out-of-bounds read in core sequence parsing logic, causing DoS. A malformed file can have stco.entry_count == 0 (creating no chunks) while still passing validation because saio.entry_count == 0 matches, but with saiz.sample_count > 0 the SampleAuxInfoReader constructor still enters its loop. This leads to an out-of-bounds dereference on the empty chunks[0] in chunked mode.
- Published
- May 22, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-125
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| struktur | libheif | cpe:2.3:a:struktur:libheif |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
strukturag libheif
- < 1.22.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- struktur libheifbefore 1.22.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libheif | from 0 | — |
| Debian:14 | libheif | before 1.23.1-1 | 1.23.1-1 |
| openSUSE:Leap 16.0 | libheif | before 1.23.0-160000.1.1 | 1.23.0-160000.1.1 |
| openSUSE:Tumbleweed | libheif | before 1.22.2-1.1 | 1.22.2-1.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | libheif | before 1.23.0-150700.3.15.1 | 1.23.0-150700.3.15.1 |
| SUSE:Linux Enterprise Server 16.0 | libheif | before 1.23.0-160000.1.1 | 1.23.0-160000.1.1 |
Same product
struktur: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11471libheif 1.4.0 has a use-after-free in heif::HeifContext::Image::set_alpha_channel in heif_context.h because heif_context.cc mishandles…36Monitor
- CVE-2026-32740libheif: Heap-Buffer-Overflow Write in Grid Tile Chroma Compositing35Monitor
- CVE-2023-49464libheif v1.17.5 was discovered to contain a segmentation violation via the function UncompressedImageCodec::get_luma_bits_per_pixel_from_con…35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-32738May 19, 2026 · libheif has a Heap OOB Read/SEGV Crash via Zero samples_per_chunk26Monitor
- ← EarlierCVE-2026-32739May 19, 2026 · libheif is Vulnerable to Infinite Loop DoS via stts Sample Duration Lookup26Monitor
- Later →CVE-2026-41071May 22, 2026 · libheif: Heap buffer over-read in SampleAuxInfoReader via crafted HEIF sequence file with mismatched saiz sample count20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libheif | 1.23.1-1 · Debian:14 | Package registry (OSV) |
| opensuse:libheif | 1.22.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libheif | 1.23.0-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4802961 days apartlibheif: heap OOB read in ImageItem_Grid::decode_grid_tile via irot-induced tile-coordinate underflow28Monitor
- CVE-2025-68431144 days apartlibheif has Potential Heap Buffer Over-Read28Monitor
- CVE-2026-4725160 days apartlibheif has an incomplete fix for CVE-2026-3949: integer overflow bypass in vvdec_push_data227Monitor
- CVE-2026-327383 days apartlibheif has a Heap OOB Read/SEGV Crash via Zero samples_per_chunk26Monitor
- CVE-2026-4927128 days apartlibheif: Wrapped icef compressed-unit range check causes out-of-bounds read in uncompressed HEIF decoder26Monitor
- CVE-2026-4725460 days apartlibheif Has Heap Buffer Overflow in `Track::get_next_sample_raw_data()` -- OOB Chunk Vector Access24Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.