How severe is GHSA-95hm-pr6q-298w?

No CVSS score has been assigned to GHSA-95hm-pr6q-298w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-95hm-pr6q-298w?

GHSA-95hm-pr6q-298w affects the following packages: fast-able (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-95hm-pr6q-298w?

Update fast-able to 1.13.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95hm-pr6q-298w is resolved across your whole dependency graph.

How do I detect GHSA-95hm-pr6q-298w in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-able. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-95hm-pr6q-298w 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.

How does O3 Security protect against GHSA-95hm-pr6q-298w?

O3 pinpoints whether GHSA-95hm-pr6q-298w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-95hm-pr6q-298w actively exploited in the wild?

No public exploit code has been indexed for GHSA-95hm-pr6q-298w 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-95hm-pr6q-298w published, and has it been updated?

GHSA-95hm-pr6q-298w was published on September 15, 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.

🦀 crates.io

GHSA-95hm-pr6q-298w

fast-able is vulnerable to DoS attack through insecure method

Also known asRUSTSEC-2025-0063

Published

Sep 15, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀fast-able

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

The public accessible struct SyncVec has a public safe method get_unchecked. It accept a parameter index and used in the get_unchecked without sufficient checks as mentioned here.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`fast-able`	all versions	1.13.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fast-able. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update fast-able to 1.13.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95hm-pr6q-298w 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.
How O3 protects you
O3 pinpoints whether GHSA-95hm-pr6q-298w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-95hm-pr6q-298w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The public accessible struct SyncVec has a public safe method get_unchecked. It accept a parameter index and used in the get_unchecked without sufficient checks as mentioned [here](https://doc.rust-lang.org/std/primitive.slice.html#method.get_unchecked).

O3 Security · Impact-Aware SCA

Is GHSA-95hm-pr6q-298w in your dependencies?

O3 detects GHSA-95hm-pr6q-298w across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works