Edition of Tuesday 10 November 2026

Memory Safety Bugs in Rust Standard Library

Comments on “Memory Safety Bugs in Rust Standard Library”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Microsoft's FORGE Lab reported memory-safety bugs in Rust's core and std libraries, some triggerable from entirely safe code, found partly with its AI scanner Hyenas. They fall into three patterns: assuming code won't panic (MapWindows::clone), trusting user-written trait implementations (str::replace with a custom Pattern), and trusting process-wide OS state (process::exit, CommandExt::exec). The team rated practical exploitation of the signal-stack bug unlikely, an assessment limited to that issue. For builders, unsafe code must stay sound when caller-supplied code misbehaves. Some dates and fix details were not independently verified.

Read the original at forge-blog.github.io. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 3 of 95 with a score of 0.76. The panel rated it highest on technical depth (0.96) and new information (0.92), lowest on significance (0.74).

AI judgeJudge 2claude-haiku-5-5
Detailed, well-evidenced security research on Rust standard library soundness bugs with reproducible examples and fixes; strong technical depth and broad relevance to builders, though niche to Rust users.
AI judgeJudge 3gpt-5.6-luna
Detailed, reproducible analysis of real Rust standard-library soundness bugs, their mechanisms, fixes, and detection methodology. It is highly actionable for Rust and security practitioners, with modest promotional framing around Microsoft’s scanning products.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.76total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.74
  • Reader interest0.86
  • Audience breadth0.76
  • Practical relevance0.76
  • Substantiated0.91
  • Technical depth0.96
  • New information0.92
  • Counts against: Promotional0.16
  • Counts against: Overclaim0.14

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.680.720.820.740.14+0.24+0.177
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.780.900.900.860.12+0.26+0.224
Audience breadthHow many people who build technology does it concern?0.820.800.670.760.15+0.13+0.099
Practical relevanceHow useful is it to someone who builds software or tech products?0.680.750.850.760.17+0.22+0.167
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.920.920.900.910.02+0.05+0.046
Technical depthHow technically substantive is it?0.990.950.950.960.04+0.05+0.048
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.900.900.950.920.05+0.05+0.046
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.070.100.300.160.23−0.19−0.030
OverclaimDo the headline or conclusions claim more than the body supports?0.170.100.150.140.07−0.11−0.015
Sum of contributions+0.761
Claim-check penalty0.000
Total, as published0.761

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #3 on Rubric, 10 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-10/3/"><img src="https://rubric.hrih.si/badge/2026-11-10/3.svg" alt="Ranked #3 on Rubric, 10 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 4 matches source · 1 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. Matches sourceFirst, only or fastest

    Microsoft made Rust a Tier-1 internal language alongside C++, C#, and TypeScript.

    The cited source says the same thing.

    The article says

    “Microsoft made Rust a Tier-1 internal language alongside C++, C#, and TypeScript”

    The source says

    “Today, Rust sits among C++, C#, and TypeScript as one of the best-supported languages for internal development at Microsoft. This “Tier-1 language” engineering status”

    Source cited by the article: rustfoundation.org/media/guest-post-rust-is-tier-1-language-at-microsoft

  2. Matches sourceNumber

    GitHub rewrote the Copilot agent runtime in Rust.

    The cited source says the same thing.

    The article says

    “GitHub rewrote the Copilot agent runtime in Rust”

    The source says

    “Using the GitHub Copilot app and the Copilot CLI, we completely rewrote the runtime into more than 800,000 lines of production Rust”

    Source cited by the article: github.blog/ai-and-ml/generative-ai/migrating-the-github-copilot-runtime-to-rust-using-copilot

  3. Couldn’t checkDate

    The Allocator API stabilization, shipping in Rust 1.100 on November 12, requires implementors never to unwind from the trait's methods or from drop.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “the stabilization, shipping in Rust 1.100 on November 12, instead requires implementors never to unwind from the trait’s methods or from drop”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/rust-lang/rust/pull/156882

  4. Matches sourceQuote

    The Allocator stabilization proposal states that unwinding out of many allocation-related methods was found to be a pervasive source of unsoundness.

    The cited source says the same thing.

    The article says

    “unwinding out of many allocation-related methods was found to be a pervasive source of unsoundness”

    The source says

    “unwinding out of many allocation-related methods was found to be a pervasive source of unsoundness”

    Source cited by the article: github.com/rust-lang/rust/pull/156882

  5. Couldn’t checkDate

    In 2020 Microsoft's team reported that str join trusted Borrow::borrow to return the same string on each call (CVE-2020-36323), and in April 2026 the same function needed another fix for a growing first element causing a heap overflow.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “In April 2026, the same function needed another fix: join borrows the first element twice, and if it grows on the second call, the remaining-length calculation underflows into a heap…”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/rust-lang/rust/pull/155708

  6. Couldn’t checkDate

    The process::exit signal stack bug dates back to 2015 and was in the standard library for nearly 11 years.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “The process::exit signal stack bug was in the standard library for nearly 11 years”

    The source says

    No passage could be compared.

    Source cited by the article: github.com/rust-lang/rust/pull/28069

  7. Matches sourceGeneralization

    Microsoft's testing of issue #161018 found no reliable exploitation path, and practical exploitation was assessed as unlikely.

    The cited source says the same thing.

    The article says

    “our testing found no reliable exploitation path under the conditions examined, and we assessed practical exploitation as unlikely”

    The source says

    “After investigation, I concluded that it is theoretically possible but practically impossible”

    Source cited by the article: github.com/rust-lang/rust/issues/161018

  8. No source givenCausal conclusion

    CommandExt::exec has written environ under only a read lock since the environment lock became a read-write lock in 2021, after a 2018 fix had held an exclusive lock.

    The article gives no link or citation for it.

    The article says

    “A 2018 fix held an exclusive lock here, but when the environment lock became a read-write lock in 2021, exec kept the read side”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Memory Safety Bugs in Rust Standard Library”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.