How severe is GHSA-jqcp-xc3v-f446?

No CVSS score has been assigned to GHSA-jqcp-xc3v-f446 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jqcp-xc3v-f446?

GHSA-jqcp-xc3v-f446 affects the following packages: fast-float2 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-jqcp-xc3v-f446?

Update fast-float2 to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqcp-xc3v-f446 is resolved across your whole dependency graph.

How do I detect GHSA-jqcp-xc3v-f446 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-float2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jqcp-xc3v-f446 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-jqcp-xc3v-f446 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jqcp-xc3v-f446 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-jqcp-xc3v-f446 published, and has it been updated?

GHSA-jqcp-xc3v-f446 was published on January 29, 2025 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-jqcp-xc3v-f446: fast-float2

Real-World Exposure

1 pkg affected

🦀fast-float2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

In this case, the "fast_float2::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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`fast-float2`	all versions	0.2.2`cargo update -p fast-float2 --precise 0.2.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-float2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fast-float2 to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqcp-xc3v-f446 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

In this case, the "fast_float2::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.

O3 Security · Impact-Aware SCA

Is GHSA-jqcp-xc3v-f446 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

fast-float2 has a segmentation fault due to lack of bound checkGHSA-jqcp-xc3v-f446