How severe is GHSA-wwq9-3cpr-mm53?

No CVSS score has been assigned to GHSA-wwq9-3cpr-mm53 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wwq9-3cpr-mm53?

GHSA-wwq9-3cpr-mm53 affects the following packages: hashbrown (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wwq9-3cpr-mm53?

Update hashbrown to 0.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwq9-3cpr-mm53 is resolved across your whole dependency graph.

How do I detect GHSA-wwq9-3cpr-mm53 in my crates.io dependencies?

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

How do I mitigate GHSA-wwq9-3cpr-mm53 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-wwq9-3cpr-mm53?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wwq9-3cpr-mm53 can be triaged on real exposure rather than presence alone.

Is GHSA-wwq9-3cpr-mm53 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wwq9-3cpr-mm53 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-wwq9-3cpr-mm53 published, and has it been updated?

GHSA-wwq9-3cpr-mm53 was published on December 4, 2024 and was last updated on September 10, 2026. 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

GHSA-wwq9-3cpr-mm53 — hashbrown

GHSA-wwq9-3cpr-mm53 is a security vulnerability in hashbrown. A fix is available for hashbrown — see the affected versions and patch details below.

Borsh serialization of HashMap is non-canonical

Also known asRUSTSEC-2024-0402

Published

Dec 4, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀hashbrown

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

This can result in consensus splits and cause equivalent objects to be considered distinct.

This was patched in 0.15.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hashbrown`	≥ 0.15.0&&< 0.15.1	0.15.1`cargo update -p hashbrown --precise 0.15.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hashbrown, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hashbrown to 0.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wwq9-3cpr-mm53 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wwq9-3cpr-mm53 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wwq9-3cpr-mm53. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding. This can result in consensus splits and cause equivalent objects to be considered distinct. This was patched in 0.15.1.

O3 Security · Impact-Aware SCA

Is GHSA-wwq9-3cpr-mm53 in your dependencies?

O3 Security finds GHSA-wwq9-3cpr-mm53 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works