Analysis of 44 uutils CVEs reveals bug classes Rust cannot prevent

An analysis of 44 CVEs found in uutils, the Rust reimplementation of GNU coreutils, reveals the classes of bugs Rust's borrow checker cannot prevent. Key vulnerability patterns include TOCTOU (Time-Of-Check-To-Time-Of-Use) race conditions from path re-resolution across syscalls, permission windows from setting permissions after creation, string equality vs filesystem identity mismatches, silent data corruption from UTF-8 coercion of raw bytes, panics as denial-of-service vectors, discarded errors, behavioral divergence from GNU tools, and trust boundary violations (e.g., loading libraries after chroot). Concrete code examples and fixes are provided for each pattern, along with actionable rules like anchoring on file descriptors, using OpenOptions::create_new, staying in bytes with OsStr, and treating every unwrap as a potential CVE. The post also highlights what Rust did prevent — zero buffer overflows, use-after-free, or data races — contrasting with GNU coreutils' history of memory-safety bugs.

Valve releases GameNetworkingSockets v1.5 with initial Rust bindings after four years

Valve has released GameNetworkingSockets v1.5, the first update in nearly four years since v1.4.1 in June 2022. The library, open-sourced in 2018, serves as a network transport layer used in games like Counter-Strike and Dota 2. The new version adds API additions, initial Rust bindings (contributed by the open-source community), peer-to-peer improvements, better CMake integration, compiler and platform compatibility fixes, security fixes, and improved CI testing. The library is available on GitHub under a BSD 3-clause license.

Warp open-sources its terminal client under AGPL v3 with MIT-licensed UI framework

<p>Warp, the AI-powered terminal built in Rust, has open-sourced its client codebase on GitHub. The UI framework crates are MIT-licensed; everything else is AGPLv3.</p>
<p>OpenAI is the founding sponsor, and agentic workflows inside Warp run on GPT models. The terminal supports its own built-in coding agent alongside third-party CLI agents like Claude Code, Codex, and Gemini CLI. Under the hood it uses Tokio, Alacritty, and other Rust crates.</p>
<h2>The contribution model is a bit unusual</h2>
<p>Warp isn’t expecting contributors to write much code directly. Instead, the workflow runs through Oz, Warp’s cloud agent orchestration platform: you file an issue, a GPT-powered agent handles implementation, and humans review and direct. The idea is that contributors act more as supervisors than coders.</p>
<p>Whether that works in practice for a community-driven project remains to be seen. It’s an interesting bet, and honestly a little strange — open-source has always been about people writing code because they care about the project. Routing that through a proprietary orchestration platform adds a layer that not everyone will be comfortable with.</p>
<h2>What else is new</h2>
<p>Alongside the open-sourcing, Warp is adding support for several open-source models: Kimi, MiniMax, and Qwen. There’s also a new <code>auto (open)</code> routing option and a programmatic settings file for better customization.</p>
<p>Warp’s CEO has been direct that the open-source move is partly competitive strategy — a way to differentiate from well-funded closed-source rivals. That’s a reasonable reason to open-source something, even if it’s not the most romantic one.</p>
<p>The repository is available on GitHub now.</p>


Warp, the Rust-based AI-powered terminal, has open-sourced its client codebase on GitHub under AGPLv3 (with UI framework crates under MIT). OpenAI is the founding sponsor, and agentic workflows run on GPT models. The contribution model is unconventional: instead of direct code contributions, contributors file issues and a GPT-powered cloud agent called Oz handles implementation while humans supervise. New open-source model support (Kimi, MiniMax, Qwen), an `auto (open)` routing option, and a programmatic settings file are also included. The CEO acknowledged the move is partly competitive strategy against well-funded closed-source rivals.

smolvm boots hardware-isolated microVMs in under 200ms on macOS and Linux

Google integrates Rust into Pixel 10 modem firmware to fix memory safety issues

Ubuntu 26.04 LTS ships Rust 1.93 and rewrites sudo and coreutils in Rust

Ubuntu audit of uutils/coreutils finds 113 issues including 70 CVEs ahead of 26.10 full rollout

An independent security audit of the uutils/coreutils project (a GNU coreutils rewrite in pure-safe-memory-safe-rust) commissioned by canonical uncovered 113 issues including 70 CVEs. Ubuntu 26.04 LTS ships with rust-coreutils 0.8 with most fixes applied, but cp, mv, and rm still fall back to GNU coreutils due to unresolved time-of-check-to-time-of-use (toctou) race conditions. Ubuntu 26.10 targets 100% rust coreutils once those remaining issues are resolved.

safe-gc implements mark-and-sweep garbage collection in Rust without any unsafe code

The author presents safe-gc, a Rust garbage collection library implemented entirely without unsafe code — no unsafe in the API, no unsafe in the implementation, enforced via forbid(unsafe_code). The library uses a mark-and-sweep algorithm with arenas backed by Vec, indexed via Gc<T> and Root<T> types rather than direct pointer derefs, which is the key design choice enabling safe Rust compliance. The post explains the heap structure, root set management, the two-level mark stack for heterogeneous types, and how classic GC footguns like dangling references and finalizer misuse are downgraded from memory-safety violations to ordinary bugs. The author also details a failed attempt at implementing a copying collector in safe Rust, explaining why heterogeneous heap types make forwarding pointers difficult to express within Rust's borrow checker.

Cloudflare adds panic and abort recovery to Rust Workers via wasm-bindgen

Cloudflare details how Rust Workers now handle panic and abort recovery in WebAssembly via upstream contributions to wasm-bindgen. Historically, panics were fatal and could poison an entire Worker instance, causing cascading failures. The team implemented panic=unwind support using the WebAssembly Exception Handling proposal, allowing panics to surface as JavaScript PanicError exceptions while keeping the Wasm instance valid. For aborts (e.g., OOM), they added abort classification using Exception.Tag to distinguish recoverable from non-recoverable errors, plus a set_on_abort hook and reentrancy guards. A --reset-state-function mechanism enables automatic reinitialization for Wasm library use cases. The team also backported modern WebAssembly Exception Handling to Node.js 24 and 22 to unblock ecosystem adoption. These changes are available in workers-rs 0.8.0 via the --panic-unwind flag, with plans to make it the default.