# GHSA-466c-pfvv-v83g: soundness issue and unmaintained

> Unmaintained Rust library lacks bounds checks in byte extraction, potentially allowing memory corruption or crashes via unsafe pointer operations.

- **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:** 2 Oct 2025
- **Also known as:** RUSTSEC-2025-0072

## What is GHSA-466c-pfvv-v83g?

GHSA-466c-pfvv-v83g is a memory corruption vulnerability in wrflib, published on 2 Oct 2025. 

### Official description

All functions under `wrflib::byte_extract` are simply wrapper of unsafe pointer offset and lacks sufficient checks to it pointer and offset parameter.

`wrflib` is unmaintained.

## Which versions are affected by GHSA-466c-pfvv-v83g?

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


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

## How do I fix GHSA-466c-pfvv-v83g?

No fix has been published for GHSA-466c-pfvv-v83g yet. Limit exposure of the affected software until one is available.

## Is GHSA-466c-pfvv-v83g being exploited?

There is no known exploitation of GHSA-466c-pfvv-v83g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-466c-pfvv-v83g and fix it if it is affected.

What it is: GHSA-466c-pfvv-v83g is a memory corruption vulnerability in wrflib, published on 2 Oct 2025. 
Exploitation: There is no known exploitation of GHSA-466c-pfvv-v83g in the wild and no public exploit code.

Affected packages and fixed versions:
- wrflib (crates.io): affected all versions up to 0.0.3; no fix listed
- wrflib (crates.io): affected all versions up to 0.0.3; no fix listed
- wrflib (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-466c-pfvv-v83g/ (Markdown: https://insights.sbomify.com/GHSA-466c-pfvv-v83g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-466c-pfvv-v83g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-466c-pfvv-v83g/
Summaries are generated and may contain mistakes; the official description above is the record.