# Announcing Rust 1.98.1 | Rust Blog
Source: [https://blog.rust-lang.org/2026/09/03/Rust-1.98.1/](https://blog.rust-lang.org/2026/09/03/Rust-1.98.1/)
The Rust team has published a new point release of Rust, 1\.98\.1\. Rust is a programming language that is empowering everyone to build reliable and efficient software\.
If you have a previous version of Rust installed via rustup, getting Rust 1\.98\.1 is as easy as:
```
rustup update stable
```
If you don't have it already, you can[get`rustup`](https://www.rust-lang.org/install.html)from the appropriate page on our website\.
## What's in 1\.98\.1
Rust 1\.98\.1 fixes a[miscompilation in vtable generation](https://github.com/rust-lang/rust/issues/161441)\.
In Rust 1\.98\.0, in some circumstances, rustc would incorrectly generate a trait object vtable with a null pointer where a function pointer should be\. This leads to undefined behavior in the emitted code\. In some cases this may 'just' cause segfaults due to the null pointer being loaded, but it is possible for it to be justification for arbitrary effects \(as is typical for UB\)\.
If you'd like to help us out by testing future releases, you might consider using the beta \(`rustup default beta`\) and nightly \(`rustup default nightly`\) channels locally and in your CI\. Please[report](https://github.com/rust-lang/rust/issues/new/choose)any bugs you might come across\!
### Contributors to 1\.98\.1
Many people came together to create Rust 1\.98\.1\. We couldn't have done it without all of you\.[Thanks\!](https://thanks.rust-lang.org/rust/1.98.1/)
Rust 1.98.0 is announced with algebraic floating-point methods for optimized operations, buffered integer formatting for performance improvements, and a fix for the interaction between ManuallyDrop and Box.
The Rust team announces Rust 1.99.0, stabilizing C-ABI variadic functions, layout information APIs from raw pointers, and updated guidance on Box::leak patterns ahead of custom allocator support.
Rust 1.98 introduces a new API to enable faster floating-point math by allowing more aggressive compiler optimizations, while still giving developers control over rounding errors.