How severe is GHSA-wwxp-hxh6-8gf8?

No CVSS score has been assigned to GHSA-wwxp-hxh6-8gf8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wwxp-hxh6-8gf8?

GHSA-wwxp-hxh6-8gf8 affects the following packages: binary_vec_io (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wwxp-hxh6-8gf8?

The records we use list no patched version of binary_vec_io for GHSA-wwxp-hxh6-8gf8. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-wwxp-hxh6-8gf8 in my crates.io dependencies?

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

How do I mitigate GHSA-wwxp-hxh6-8gf8 if there is no patch (or I can't update yet)?

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.

Is GHSA-wwxp-hxh6-8gf8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wwxp-hxh6-8gf8 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-wwxp-hxh6-8gf8 published, and has it been updated?

GHSA-wwxp-hxh6-8gf8 was published on October 22, 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

binary_vec_io access memory out-of-bounds in binary_read_to_ref and binary_write_from_refGHSA-wwxp-hxh6-8gf8

Fix: RustSec/advisory-db#2428

GHSA-wwxp-hxh6-8gf8 is a security vulnerability in binary_vec_io. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0109

Published

Oct 22, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀binary_vec_io

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

Safe functions accept a single &T or &mut T but multiply by n to create slices extending beyond allocated memory when n > 1.

These functions use from_raw_parts to create slices larger than the underlying allocation, violating memory safety.

The binary_vec_io repository is archived and unmaintained.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`binary_vec_io`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for binary_vec_io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of binary_vec_io for GHSA-wwxp-hxh6-8gf8. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

Safe functions accept a single `&T` or `&mut T` but multiply by `n` to create slices extending beyond allocated memory when `n > 1`. These functions use `from_raw_parts` to create slices larger than the underlying allocation, violating memory safety. The binary_vec_io repository is archived and unmaintained.

O3 Security · Impact-Aware SCA

Is GHSA-wwxp-hxh6-8gf8 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works