How severe is GHSA-m325-rxjv-pwph?

No CVSS score has been assigned to GHSA-m325-rxjv-pwph yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m325-rxjv-pwph?

GHSA-m325-rxjv-pwph affects the following packages: messagepack-rs (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-m325-rxjv-pwph?

The records we use list no patched version of messagepack-rs for GHSA-m325-rxjv-pwph. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-m325-rxjv-pwph in my crates.io dependencies?

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

How do I mitigate GHSA-m325-rxjv-pwph if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-m325-rxjv-pwph actively exploited in the wild?

No public exploit code has been indexed for GHSA-m325-rxjv-pwph 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-m325-rxjv-pwph?

GHSA-m325-rxjv-pwph has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th 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.

What type of vulnerability is GHSA-m325-rxjv-pwph?

GHSA-m325-rxjv-pwph is classified as CWE-908 (CWE-908). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m325-rxjv-pwph published, and has it been updated?

GHSA-m325-rxjv-pwph was published on June 17, 2022 and was last updated on March 15, 2024. 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

Deserialization functions pass uninitialized memory to user-provided ReadGHSA-m325-rxjv-pwph

GHSA-m325-rxjv-pwph is a CWE-908 vulnerability in messagepack-rs. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2021-45690 CVE-2021-45691 CVE-2021-45692 CVE-2021-45693 GHSA-hr52-f9vp-582c GHSA-jqjj-r4qp-x2gh

Published

Jun 17, 2022

Updated

Mar 15, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🦀messagepack-rs

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

Affected versions of this crate passed an uninitialized buffer to a user-provided Read instance in:

deserialize_binary
deserialize_string
deserialize_extension_others
deserialize_string_primitive

This can result in safe Read implementations reading from the uninitialized buffer leading to undefined behavior.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`messagepack-rs`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

messagepack-rsmessagepack-rs_project

< 0.8.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for messagepack-rs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of messagepack-rs for GHSA-m325-rxjv-pwph. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

Affected versions of this crate passed an uninitialized buffer to a user-provided `Read` instance in: * `deserialize_binary` * `deserialize_string` * `deserialize_extension_others` * `deserialize_string_primitive` This can result in safe `Read` implementations reading from the uninitialized buffer leading to undefined behavior.

O3 Security · Impact-Aware SCA

Is GHSA-m325-rxjv-pwph in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works