# GHSA-wv8j-m3hx-924j: Arrow2 allows out of bounds access in public safe API

> Out-of-bounds access in arrow2's public API allows attackers to cause memory corruption or crashes; users must migrate to the maintained arrow crate.

- **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:** 24 Apr 2025
- **Also known as:** RUSTSEC-2025-0038

## What is GHSA-wv8j-m3hx-924j?

GHSA-wv8j-m3hx-924j is a memory corruption vulnerability in arrow2, published on 24 Apr 2025. 

### Official description

`Rows::row_unchecked()` allows out of bounds access to the underlying buffer without sufficient checks.

The arrow2 crate is no longer maintained, so there are no plans to fix this issue. Users are advised to migrate to the arrow crate, instead.

## Which versions are affected by GHSA-wv8j-m3hx-924j?

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


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

## How do I fix GHSA-wv8j-m3hx-924j?

No fix has been published for GHSA-wv8j-m3hx-924j yet. Limit exposure of the affected software until one is available.

## Is GHSA-wv8j-m3hx-924j being exploited?

There is no known exploitation of GHSA-wv8j-m3hx-924j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wv8j-m3hx-924j and fix it if it is affected.

What it is: GHSA-wv8j-m3hx-924j is a memory corruption vulnerability in arrow2, published on 24 Apr 2025. 
Exploitation: There is no known exploitation of GHSA-wv8j-m3hx-924j in the wild and no public exploit code.

Affected packages and fixed versions:
- arrow2 (crates.io): affected all versions up to 0.18.0; no fix listed
- arrow2 (crates.io): affected all versions up to 0.18.0; no fix listed
- arrow2 (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-wv8j-m3hx-924j/ (Markdown: https://insights.sbomify.com/GHSA-wv8j-m3hx-924j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wv8j-m3hx-924j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wv8j-m3hx-924j/
Summaries are generated and may contain mistakes; the official description above is the record.