<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>FORGE Lab</title><link>https://forge-blog.github.io/</link><description>Recent content on FORGE Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 09 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://forge-blog.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Memory Safety Bugs in Rust Standard Library</title><link>https://forge-blog.github.io/posts/rust-std-memory-safety/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://forge-blog.github.io/posts/rust-std-memory-safety/</guid><description>&lt;p&gt;Microsoft&amp;rsquo;s FORGE Lab found several memory safety issues in Rust&amp;rsquo;s standard library (&lt;code&gt;std&lt;/code&gt; and &lt;code&gt;core&lt;/code&gt;), including cases where code written entirely in safe Rust can trigger undefined behavior. The research used Hyenas, FORGE&amp;rsquo;s frontier research version of codename MDASH, an AI-powered vulnerability-scanning system. The findings reveal three recurring patterns of misplaced trust in unsafe code: trusting code not to panic, trusting user-provided implementations to be correct, and trusting the underlying system.&lt;/p&gt;</description></item></channel></rss>