Rust 1.94.1 is a point release that addresses several regressions introduced in version 1.94.0, along with a security fix. This update is recommended for all users. If you already have Rust installed via rustup, simply run rustup update stable to upgrade. Below, we answer common questions about what’s new in this patch.

How do I update to Rust 1.94.1?

Updating to the latest stable release is straightforward. Open your terminal and run:

rustup update stable

This command will fetch Rust 1.94.1 and set it as your default toolchain. If you don’t have rustup installed, you can get it from the official Rust website. The process takes only a few seconds and your existing projects will continue to work seamlessly.

What regressions were fixed in Rust 1.94.1?

This point release resolves three regressions that were accidentally introduced in Rust 1.94.0:

• Fix std::thread::spawn on wasm32-wasip1-threads – A bug that prevented spawning threads on this WebAssembly target was corrected.
• Removed new methods from std::os::windows::fs::OpenOptionsExt – Unstable extension methods were added in 1.94.0, but the trait is not sealed, making extension impossible. These were reverted.
• Clippy: fix ICE in match_same_arms – An internal compiler error (ICE) that occurred when using Clippy’s match_same_arms lint was fixed.
• Cargo: downgraded curl-sys to 0.4.83 – This addresses certificate validation errors on some FreeBSD versions.

Why was the std::thread::spawn fix important for WebAssembly?

The wasm32-wasip1-threads target allows Rust programs to use native threads on WebAssembly runtimes that support the WASI threading model. The regression in 1.94.0 broke std::thread::spawn, causing applications that rely on multi-threading to fail. By fixing this, Rust 1.94.1 restores the ability to build concurrent WebAssembly modules. This is especially important for developers working on server-side Wasm or high-performance web applications that need parallelism.

What happened with the OpenOptionsExt new methods on Windows?

In Rust 1.94.0, unstable methods were added to std::os::windows::fs::OpenOptionsExt. However, because the trait is not sealed, it cannot be extended with non-default methods without breaking backward compatibility. The Rust team decided to remove these methods to preserve the trait’s extensibility and avoid future issues. Developers who were using these unstable features may need to adjust their code, but no stable API was affected.

What was the Clippy ICE fix about?

The Clippy lint match_same_arms detects when multiple match arms have identical bodies. In Rust 1.94.0, running this lint could trigger an internal compiler error (ICE), crashing Clippy. The fix in 1.94.1 corrects the span handling within the lint, so it now runs reliably. This allows developers to continue using Clippy’s powerful code quality checks without unexpected crashes.

What security fixes are included in this release?

Cargo has updated the tar dependency to version 0.4.45 to resolve two vulnerabilities: CVE-2026-33055 and CVE-2026-33056. These CVEs affect how tar archives are extracted, but users of crates.io are not impacted directly. The fix ensures that Cargo’s archive handling remains secure. Additionally, the downgrade of curl-sys to version 0.4.83 resolves certificate validation failures on some FreeBSD systems. No other security changes were made.

Who contributed to Rust 1.94.1?

Many community members and the Rust team collaborated to deliver this point release. Contributors filed bug reports, submitted patches, and reviewed changes. The Rust project thanks everyone who helped identify and fix these regressions and security issues. Without such active community involvement, delivering a stable and secure toolchain would be far more challenging. If you’re interested in contributing, check out the Rust repository on GitHub.