cargo package report

Is mio safe?

2 known vulnerabilities, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
0.90%

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-r8w9-5wcg-vfj7, the advisory selected below

// advisories

GHSA-r8w9-5wcg-vfj7

HIGHCVE-2024-27308

When using named pipes on Windows, mio will under some circumstances return invalid tokens that correspond to named pipes that have already been deregistered from the mio registry. The impact of this vulnerability depends on how mio is used. For some applications, invalid tokens may be ignored or cause a warning or a crash. On the other hand, for applications that store pointers in the tokens, thi

Affected
>=0.7.2, <0.8.11
Fixed in
0.8.11
Weakness
CWE-416
Published
2024-03-04
Source
github

GHSANVDMITRE

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

Checked 2026-09-22 at 01:43 UTC. The most recent advisory here was published 2024-03-04. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is mio safe? cargo package security report | CyberXYZ