- Exploited
- No known exploitation
- Fix
- Fixed in 0.3.27
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.3.27.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The heifer-isobmff library (and the heifer crate built on it) can be made to run out of memory when parsing a specially crafted HEIF/HEIC file, which can crash the process. Any application that parses untrusted HEIF/HEIC files through HeifFile::parse or the functions built on it is affected, and the problem is fixed in version 0.3.27.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
heifer-isobmff read the item and extent counts of the iloc box (item locations) from the file and allocated memory for them before checking that the box was large enough to hold that many entries. Extents that declare no field at all take zero bytes each, so a small crafted file could declare an enormous number of them. A 42 KB file made parsing allocate several gigabytes, which can exhaust memory and abort the process.
Any application that parses untrusted HEIF/HEIC files with heifer-isobmff, directly or through the heifer crate, is affected: HeifFile::parse and every decoding and metadata function built on it.
The flaw was corrected in 0.3.27 (commit `1a8426e`): item and extent counts are bounded by the size of the box, extents that carry no field are rejected, and the total number of extents is capped.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects crates.io packages
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.3.27.
Timeline
- Advisory published5 days
- Record last updated
Affected versions
- heifer-isobmffcrates.io
From 0.0.0-0 · fixed in 0.3.27
Evidence 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about RUSTSEC-2026-0458
Is RUSTSEC-2026-0458 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by RUSTSEC-2026-0458?
heifer-isobmff (crates.io): from 0.0.0-0 before 0.3.27.Source: cve.now feed data
How do I fix RUSTSEC-2026-0458?
Upgrade to a fixed version: 0.3.27.Source: cve.now feed data