A Rust lifetime bug can let safe code retain an expired reference

A Rust compiler issue shows field assignment bypassing a struct’s lifetime requirements, allowing a destructor to retain a reference after its data expires. The report includes examples that compile without unsafe blocks and trigger invalid memory access. Maintainers classify it as high-priority unsoundness, while stressing that exploitation needs a deliberately malicious Drop implementation; they consider accidental triggering unlikely.

Rust issue tracker · Oct 13, 2026

Why it matters

Memory-safety guarantees depend on compiler correctness as well as how application code is written.

More context

Watch the linked issue and fix work for release guidance. The report demonstrates affected stable and nightly compilers, but does not establish a released fix to recommend today.

Keep in mind

A reproducible compiler soundness hole is serious, but this report is not evidence of widespread exploitation in deployed applications.

Original read