NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

Improper Synchronization and Race Condition in vm-memoryGHSA-mm4m-qg48-f7wc

HIGH

GHSA-mm4m-qg48-f7wc is a high-severity (CVSS 7.5) CWE-362 vulnerability in vm-memory. A fix is available for vm-memory — see the affected versions and patch details below.

Also known asCVE-2020-13759RUSTSEC-2020-0157
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk
0.00%0.71%1.43%2.14%0.4%1.6%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🦀vm-memory🦀vm-memory

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

rust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iovm-memoryall versions0.1.1cargo update -p vm-memory --precise 0.1.1
🦀crates.iovm-memory≥ 0.2.0&&< 0.2.10.2.1cargo update -p vm-memory --precise 0.2.1

Affected Products

1 product · 2 configurations
Application
vm-memoryvm-memory_project
≥ 0.2.0 && < 0.2.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update vm-memory to 0.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm4m-qg48-f7wc is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

rust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).
O3 Security · Impact-Aware SCA

Is GHSA-mm4m-qg48-f7wc in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Synchronization and Race Condition in…