Every CVE Search/ Get API key

OSV-2025-788

Heap-buffer-overflow in int arrow::bit_util::BitReader::GetBatch<int>

No scoreFix available

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=447480433

Crash type: Heap-buffer-overflow READ 8
Crash state:
int arrow::bit_util::BitReader::GetBatch<int>
auto arrow::util::RleBitPackedDecoder<int>::GetBatch
std::__1::pair<int, arrow::util::RleBitPackedParser::ControlFlow> arrow::util::R

What each source reports

OSV No score

Heap-buffer-overflow in int arrow::bit_util::BitReader::GetBatch<int>

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=447480433

Crash type: Heap-buffer-overflow READ 8
Crash state:
int arrow::bit_util::BitReader::GetBatch<int>
auto arrow::util::RleBitPackedDecoder<int>::GetBatch
std::__1::pair<int, arrow::util::RleBitPackedParser::ControlFlow> arrow::util::R
Record
OSV-2025-788
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
arrow
OSS-Fuzz
Commit ranges
Not evaluated

Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.

History

History
RecordedChangedSources
first indexedOSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

OSV-2025-788 is a vulnerability with no CVSS score yet in arrow, published September 28, 2025. No source lists public exploit code. A source reports a fix.

References

MoveEnter Open