NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
CRITICAL severity

Use of Uninitialized Resource in ashGHSA-64wv-8vwp-xgw2

CRITICALFix: ash-rs/ash#470

GHSA-64wv-8vwp-xgw2 is a critical-severity (CVSS 9.8) CWE-908 vulnerability in ash. A fix is available for ash — see the affected versions and patch details below.

Also known asCVE-2021-45688GHSA-qj69-c89v-jwq2RUSTSEC-2021-0090
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk+0.04%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.84%1.19%1.54%1.89%1.3%1.3%1.3%1.3%1.4%Jul 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🦀ash

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

An issue was discovered in the ash crate before 0.33.1 for Rust. util::read_spv may read from uninitialized memory locations.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioashall versions0.33.1cargo update -p ash --precise 0.33.1

Affected Products

1 product · 1 configurations
Application
ashash-rs
< 0.33.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update ash to 0.33.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-64wv-8vwp-xgw2 is resolved across your whole dependency graph.

  3. 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

An issue was discovered in the ash crate before 0.33.1 for Rust. util::read_spv may read from uninitialized memory locations.
O3 Security · Impact-Aware SCA

Is GHSA-64wv-8vwp-xgw2 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
Use of Uninitialized Resource in ash (Critical 9.8)