GHSA-r7cj-wmwv-hfw5 — arrow
GHSA-r7cj-wmwv-hfw5 is a security vulnerability in arrow. A fix is available for arrow — see the affected versions and patch details below.
`BinaryArray` does not perform bound checks on reading values and offsets
Real-World Exposure
arrowReal-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
BinaryArray performs insufficient validation on creation, which allows out-of-bounds reads in safe code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | arrow | all versions | 6.4.0cargo update -p arrow --precise 6.4.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for arrow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update arrow to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7cj-wmwv-hfw5 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r7cj-wmwv-hfw5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r7cj-wmwv-hfw5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r7cj-wmwv-hfw5 in your dependencies?
O3 Security finds GHSA-r7cj-wmwv-hfw5 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.