RUSTSEC-2026-0306None▾ Sunlit`hex_decode_unchecked` AVX2 path reads past `src`
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
faster_hex::hex_decode_unchecked is a safe function. On x86 and x86_64, when AVX2 is enabled, hex_decode_avx2 keeps decoding while dst.len() >= 32 and then loads 32 bytes from src and 32 bytes from src[32..]. Nothing in that loop requires src to contain 64 bytes.
A safe caller can pass a short src and a dst of at least 32 bytes. The AVX2 load then reads outside src.
The function has had this shape since 0.3.0. 0.10.0 is the last release with the unbounded AVX2 read. The maintainer agreed to this advisory and shipped the backport in 0.10.1 (pull request 74): the AVX2 loop now requires src.len() >= 64 before those loads. 1.0.0 rewrites hex_decode_unchecked so the decoded length is min(src.len() / 2, dst.len()). Both are covered by >= 0.10.1. Other architectures take the scalar fallback and are outside this advisory.
faster-hex >= 0.3.0, < 0.10.1Upgrade to a patched release:
faster-hex 0.10.1