GHSA-8655-xgh5-5vvq
fast-fault has a segmentation fault due to lack of bound check
In this case, the "fast_float::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.
No patched version for fast-float crate has been released, but a patch is available in the fast-float2 fork.
What each source reports
GitHub AdvisoriesNo score
fast-fault has a segmentation fault due to lack of bound check
In this case, the "fast_float::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.
No patched version for fast-float crate has been released, but a patch is available in the fast-float2 fork.
- Record
GHSA-8655-xgh5-5vvq- Updated
- 2026-11-02
OSVNo score
fast-fault has a segmentation fault due to lack of bound check
In this case, the "fast_float::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.
No patched version for fast-float crate has been released, but a patch is available in the fast-float2 fork.
- Record
GHSA-8655-xgh5-5vvq- Updated
- 2026-11-02
OSVRUSTSEC-2025-0003No score
Segmentation fault due to lack of bound check
In this case, the "fast_float::common::AsciiStr::first" method within the "AsciiStr" struct uses the unsafe keyword to reading from memory without performing bounds checking. Specifically, it directly dereferences a pointer offset by "self.ptr". Because of the above reason, the method accesses invalid memory address when it takes an empty string as its input. This approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.
No patched version for fast-float crate has been released, but a patch is available in the fast-float2 fork.
- Record
RUSTSEC-2025-0003- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
fast-floatcrates.io | through 0.2.0 | None known |
fast-floatcrates.io | 0.0.0-0 and later | None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-8655-xgh5-5vvq is a vulnerability with no CVSS score yet in fast-float, published January 13, 2025. No source lists public exploit code. No source names a fixed version.