Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-m325-rxjv-pwph — messagepack-rs

GHSA-m325-rxjv-pwph is a CWE-908 vulnerability in messagepack-rs. No vendor fix is recorded yet; mitigation options are listed below.

Deserialization functions pass uninitialized memory to user-provided Read

Also known asCVE-2021-45690CVE-2021-45691CVE-2021-45692CVE-2021-45693GHSA-hr52-f9vp-582cGHSA-jqjj-r4qp-x2gh
Published
Jun 17, 2022
Updated
Mar 15, 2024
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 18, 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 CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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
EcosystemPackageVulnerable rangeFix
🦀crates.iomessagepack-rsall versionsNo fix

Detection & mitigation playbook

Open-source dependency

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

  2. Remediation status

    No patched version of messagepack-rs has shipped for GHSA-m325-rxjv-pwph yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

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

Tailored to GHSA-m325-rxjv-pwph. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-m325-rxjv-pwph 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
GHSA-m325-rxjv-pwph: messagepack-rs | O3 Security