Advisory

RUSTSEC-2026-0198

Also known as: None

Summary

Report::frames_mut allows aliased mutable references

Details

Affected versions of this crate return an iterator from
Report::frames_mut whose &mut Frame items have lifetimes independent
of the iterator, so all yielded references can be held at the same time.
A yielded frame's sources are also yielded by the iterator and reachable
through the parent frame via Frame::sources_mut, allowing safe code to
obtain two live mutable references to the same frame. This is undefined
behavior and can be used to cause a segmentation fault (see reproducer in
the linked issue). Versions 0.1.0 and 0.1.1 are affected through
Frame::source_mut instead of Frame::sources_mut.

The flaw is fixed in 0.8.0 by replacing the iterator with internal
iteration: Report::frames_mut now takes a visitor closure, so mutable
access to a frame is scoped and cannot overlap with access to its
sources.

Severity

Not rated by the source.

Dates

Published
2026-07-03 12:00 UTC
Modified
2026-07-03 15:34 UTC

Affected packages and fixes

error-stack

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.8.0 (semver)

Fixed versions

0.8.0

Fix

  • Fixed version 0.8.0
    cargo update -p error-stack --precise 0.8.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences