GHSA-cjw4-2w9r-r8mv — pyarrow
HIGHGHSA-cjw4-2w9r-r8mv is a high-severity (CVSS 7.5) CWE-909 vulnerability in pyarrow. A fix is available for pyarrow — see the affected versions and patch details below.
Missing Initialization of Resource in Apache Arrow
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-cjw4-2w9r-r8mv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
pyarrow💎red-arrowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI, RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
While investigating UBSAN errors in https://github.com/apache/arrow/pull/5365 it was discovered Apache Arrow versions 0.12.0 to 0.14.1, left memory Array data uninitialized when reading RLE null data from parquet. This affected the C++, Python, Ruby and R implementations. The uninitialized memory could potentially be shared if are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pyarrow | ≥ 0.12.0&&< 0.15.1 | 0.15.1pip install --upgrade 'pyarrow==0.15.1' |
| 💎RubyGems | red-arrow | ≥ 0.12.0&&< 0.15.1 | 0.15.1bundle update red-arrow --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pyarrow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pyarrow to 0.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cjw4-2w9r-r8mv 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-cjw4-2w9r-r8mv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-cjw4-2w9r-r8mv. 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-cjw4-2w9r-r8mv in your dependencies?
O3 Security finds GHSA-cjw4-2w9r-r8mv across PyPI, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.