Rust's famous compile-time safety net had a decade-plus hole nobody noticed.
A GitHub issue filed against the rust-lang/rust repository documents unsoundness bugs in the language's borrow checker that have existed for 11 years. The report surfaced on Hacker News on October 13, 2026, where it picked up 64 points and 15 comments. The issue lives in the project's own public tracker, the same place developers go to file and track compiler defects. At the time of writing, the thread remains the primary public record of the finding.
Rust built its reputation on the promise that the borrow checker catches memory errors before code ever runs. An unsoundness bug means the checker can wave through code it should have rejected - a crack in the exact guarantee developers migrate to Rust for. A flaw sitting unnoticed for over a decade says less about carelessness and more about how hard it is to formally verify every edge case in a system this complex.
Every memory-safe language eventually finds its own asterisk; Rust just found one of its oldest.