- 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-hevc-dec Rust crate, and the heifer crate that depends on it, can crash when decoding a crafted HEIC or HEVC stream whose tile layout does not fit the picture size. An attacker can cause a panic that aborts the decoding thread, or the whole process if it is built with panic = "abort", and can also cause a picture to be decoded incorrectly.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
An HEVC picture parameter set (PPS) stores explicit tile column widths and row heights computed against the sequence parameter set (SPS) active when it was parsed. A crafted stream can redefine that SPS afterwards, so that the tile sizes add up to more than the picture. The decoder then indexed past its coding tree block tables: Rust's bounds checks turned this into a panic, or the picture was decoded wrongly. A panic aborts the decoding thread, or the whole process when built with panic = "abort". The crate forbids unsafe code, so there is no memory corruption.
Any application that decodes untrusted HEIC files or HEVC streams with heifer-hevc-dec, directly or through the heifer crate, is affected.
The flaw was corrected in 0.3.27 (commit `71dfc67`): a tile layout that does not match the picture size is rejected with Error::Invalid at decode time.
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-hevc-deccrates.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-0456
Is RUSTSEC-2026-0456 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-0456?
heifer-hevc-dec (crates.io): from 0.0.0-0 before 0.3.27.Source: cve.now feed data
How do I fix RUSTSEC-2026-0456?
Upgrade to a fixed version: 0.3.27.Source: cve.now feed data