# GHSA-wwxp-hxh6-8gf8: binary_vec_io access memory out-of-bounds in binary_read_to_ref and binary_write_from_ref

> Safe functions in the archived binary_vec_io library allow out-of-bounds memory access, potentially leading to crashes or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2025
- **Also known as:** RUSTSEC-2025-0109

## What is GHSA-wwxp-hxh6-8gf8?

GHSA-wwxp-hxh6-8gf8 is a memory corruption vulnerability in binary_vec_io, published on 21 Oct 2025. 

### Official 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.

## Which versions are affected by GHSA-wwxp-hxh6-8gf8?

3 open source packages ship an affected version, including binary_vec_io.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `binary_vec_io` | crates.io | All versions to 0.1.12 | None |
| `binary_vec_io` | crates.io | All versions to 0.1.12 | None |
| `binary_vec_io` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for GHSA-wwxp-hxh6-8gf8 yet. Limit exposure of the affected software until one is available.

## Is GHSA-wwxp-hxh6-8gf8 being exploited?

There is no known exploitation of GHSA-wwxp-hxh6-8gf8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wwxp-hxh6-8gf8 and fix it if it is affected.

What it is: GHSA-wwxp-hxh6-8gf8 is a memory corruption vulnerability in binary_vec_io, published on 21 Oct 2025. 
Exploitation: There is no known exploitation of GHSA-wwxp-hxh6-8gf8 in the wild and no public exploit code.

Affected packages and fixed versions:
- binary_vec_io (crates.io): affected all versions up to 0.1.12; no fix listed
- binary_vec_io (crates.io): affected all versions up to 0.1.12; no fix listed
- binary_vec_io (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-wwxp-hxh6-8gf8/ (Markdown: https://insights.sbomify.com/GHSA-wwxp-hxh6-8gf8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wwxp-hxh6-8gf8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wwxp-hxh6-8gf8/
Summaries are generated and may contain mistakes; the official description above is the record.