Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0123 json

Out-of-bounds read in `bytes_helper` public safe functions

published 6mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

The `bytes_helper` module contains multiple public functions (`into_arr4()`, `into_arr2()`, `u8_from_le_bytes()`) that use `slice.get_unchecked(pos..pos + N)` without verifying that `pos + N <= slice.len()`. These are public safe API functions, allowing any caller to trigger undefined behavior by passing invalid positions.

For example, calling `into_arr4(&data, 10)` where `data` is a 3-byte slice causes an out-of-bounds access since position 10 exceeds the slice length.

Patch / fix

  • crates.io rustdx 0.4.4

Is RUSTSEC-2026-0123 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io rustdx
>=0.0.0-0, <0.4.4
0.4.4

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.