How severe is GHSA-pfp7-vxgr-83pw?

No CVSS score has been assigned to GHSA-pfp7-vxgr-83pw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pfp7-vxgr-83pw?

GHSA-pfp7-vxgr-83pw affects the following packages: toodee (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-pfp7-vxgr-83pw?

Update toodee to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfp7-vxgr-83pw is resolved across your whole dependency graph.

How do I detect GHSA-pfp7-vxgr-83pw in my crates.io dependencies?

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

How do I mitigate GHSA-pfp7-vxgr-83pw if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-pfp7-vxgr-83pw?

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

Is GHSA-pfp7-vxgr-83pw actively exploited in the wild?

No public exploit code has been indexed for GHSA-pfp7-vxgr-83pw 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.

When was GHSA-pfp7-vxgr-83pw published, and has it been updated?

GHSA-pfp7-vxgr-83pw was published on September 9, 2025 and was last updated on October 28, 2025. 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

GHSA-pfp7-vxgr-83pw — toodee

Fix: antonmarsden/toodee@e6e16d5

GHSA-pfp7-vxgr-83pw is a remote code execution vulnerability in toodee. A fix is available for toodee — see the affected versions and patch details below.

toodee is vulnerable to Heap Buffer Overflow through its DrainCol Destructor

Also known asRUSTSEC-2025-0062

Published

Sep 9, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀toodee

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

An off-by-one error in the DrainCol::drop destructor could cause an unsafe memory copy operation to exceed the bounds of the associated vector.

The error was related to the size of the data being copied in one of the ptr::copy invocations inside the destructor.

When removing the first column from a TooDee object, the DrainCol return object could cause a heap buffer overflow vulnerability when it is dropped.

The issue was fixed in commit e6e16d5 by reducing the copied size by one.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`toodee`	≥ 0.2.0&&< 0.6.0	0.6.0`cargo update -p toodee --precise 0.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for toodee, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update toodee to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfp7-vxgr-83pw is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pfp7-vxgr-83pw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pfp7-vxgr-83pw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An off-by-one error in the `DrainCol::drop` destructor could cause an unsafe memory copy operation to exceed the bounds of the associated vector. The error was related to the size of the data being copied in one of the `ptr::copy` invocations inside the destructor. When removing the first column from a TooDee object, the DrainCol return object could cause a heap buffer overflow vulnerability when it is dropped. The issue was fixed in commit `e6e16d5` by reducing the copied size by one.

O3 Security · Impact-Aware SCA

Is GHSA-pfp7-vxgr-83pw in your dependencies?

O3 Security finds GHSA-pfp7-vxgr-83pw 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