How severe is GHSA-82hm-vh7g-hrh9?

No CVSS score has been assigned to GHSA-82hm-vh7g-hrh9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-82hm-vh7g-hrh9?

GHSA-82hm-vh7g-hrh9 affects the following packages: molecule (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-82hm-vh7g-hrh9?

Update molecule to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82hm-vh7g-hrh9 is resolved across your whole dependency graph.

How do I detect GHSA-82hm-vh7g-hrh9 in my crates.io dependencies?

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

How do I mitigate GHSA-82hm-vh7g-hrh9 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-82hm-vh7g-hrh9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-82hm-vh7g-hrh9 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.

What is the EPSS score for GHSA-82hm-vh7g-hrh9?

GHSA-82hm-vh7g-hrh9 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-82hm-vh7g-hrh9 published, and has it been updated?

GHSA-82hm-vh7g-hrh9 was published on August 25, 2021 and was last updated on November 8, 2023. 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

Not in CISA KEV

Partial read is incorrect in moleculeGHSA-82hm-vh7g-hrh9

Fix: nervosnetwork/molecule#49

GHSA-82hm-vh7g-hrh9 is a security vulnerability in molecule. A fix is available for molecule — see the affected versions and patch details below.

Also known asCVE-2021-45697 GHSA-6p3c-v8vc-c244RUSTSEC-2021-0103

Published

Aug 25, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🦀molecule

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

Impact

Anyone who uses total_size(..) function to partial read the length of any FixVec will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release.

Workarounds

If you already have the whole FixVec A, you can use A.as_slice().len() to get the total size of the FixVec.

For more information

If you have any questions or comments about this advisory:

Open an issue to ask use directly.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`molecule`	all versions	0.7.2`cargo update -p molecule --precise 0.7.2`

Affected Products

1 product · 1 configurations

Application

moleculenervos

< 0.7.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for molecule, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update molecule to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82hm-vh7g-hrh9 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

### Impact Anyone who uses `total_size(..)` function to partial read the length of any `FixVec` will get an incorrect result, due to an incorrect implementation. This has been resolved in the 0.7.2 release. ### Workarounds If you already have the whole `FixVec` `A`, you can use `A.as_slice().len()` to get the total size of the `FixVec`. ### For more information If you have any questions or comments about this advisory: - [Open an issue to ask use directly](https://github.com/nervosnetwork/molecule/issues/new).

O3 Security · Impact-Aware SCA

Is GHSA-82hm-vh7g-hrh9 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works