Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-wwxp-hxh6-8gf8 binary_vec_io

Fix: RustSec/advisory-db#2428

GHSA-wwxp-hxh6-8gf8 is a security vulnerability in binary_vec_io. No vendor fix is recorded yet; mitigation options are listed below.

binary_vec_io access memory out-of-bounds in binary_read_to_ref and binary_write_from_ref

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
EcosystemPackageVulnerable rangeFix
🦀crates.iobinary_vec_ioall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Remediation status

    No patched version of binary_vec_io has shipped for GHSA-wwxp-hxh6-8gf8 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

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

Tailored to GHSA-wwxp-hxh6-8gf8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-wwxp-hxh6-8gf8 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-wwxp-hxh6-8gf8: binary_vec_io | O3 Security