How severe is CVE-2021-45687?

No CVSS score has been assigned to CVE-2021-45687 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2021-45687?

CVE-2021-45687 affects the following packages: raw-cpuid (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2021-45687?

Update raw-cpuid to 9.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-45687 is resolved across your whole dependency graph.

How do I detect CVE-2021-45687 in my crates.io dependencies?

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

How do I mitigate CVE-2021-45687 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 CVE-2021-45687 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-45687 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 CVE-2021-45687?

CVE-2021-45687 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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 CVE-2021-45687?

CVE-2021-45687 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-45687 published, and has it been updated?

CVE-2021-45687 was published on June 17, 2022 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

CVE-2021-45687 — raw-cpuid

CVE-2021-45687 is a Improper Input Validation vulnerability in raw-cpuid. A fix is available for raw-cpuid — see the affected versions and patch details below.

Optional `Deserialize` implementations lacking validation

Also known asGHSA-w428-f65r-h4q2RUSTSEC-2021-0089

Published

Jun 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🦀raw-cpuid

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

When activating the non-default feature serialize, most structs implement serde::Deserialize without sufficient validation. This allows breaking invariants in safe code, leading to:

Undefined behavior in as_string() methods (which use std::str::from_utf8_unchecked() internally).
Panics due to failed assertions.

See https://github.com/gz/rust-cpuid/issues/43.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`raw-cpuid`	≥ 3.1.0&&< 9.1.1	9.1.1`cargo update -p raw-cpuid --precise 9.1.1`

Affected Products

1 product · 1 configurations

Application

raw-cpuidraw-cpuid_project

< 9.1.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 raw-cpuid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update raw-cpuid to 9.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-45687 is resolved across your whole dependency graph.
Workarounds
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

When activating the non-default feature `serialize`, most structs implement `serde::Deserialize` without sufficient validation. This allows breaking invariants in safe code, leading to: * Undefined behavior in `as_string()` methods (which use `std::str::from_utf8_unchecked()` internally). * Panics due to failed assertions. See https://github.com/gz/rust-cpuid/issues/43.

O3 Security · Impact-Aware SCA

Is CVE-2021-45687 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works