cargo package report

Is pprof safe?

1 known vulnerability.

cvss
not scored

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
1.1

CyberXYZ composite, out of 10

fig. 01 — GHSA-gw5w-5j7f-jmjj, the advisory selected below

// advisories

GHSA-gw5w-5j7f-jmjj

UNKNOWN

The library breaks the safety assumptions when using unsafe API std::slice::fromrawparts. First, when using the API in iterator implementation (TempFdArrayIterator.next), generic type could be any type, which would create and pass a misaligned pointer to the unsafe API. Second, when validating the address, the code passed the type cvoid, which could also be any type, leading to potential uninitial

Affected
>=0.0.0-0, <0.14.0
Fixed in
0.14.0
Published
2024-12-05
Source
github

GHSA

// 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 00:39 UTC. The most recent advisory here was published 2024-12-05. Updated continuously from NVD, GHSA, OSV and CNA feeds.

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