NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI💎 RubyGems
Not in CISA KEV
HIGH severity

CVE-2019-12410 — pyarrow

HIGH

CVE-2019-12410 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

Also known asGHSA-cjw4-2w9r-r8mvPYSEC-2019-196
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk
4.11%4.67%5.22%5.78%5.3%4.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐍pyarrow💎red-arrow

Real-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

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIpyarrow≥ 0.12.0&&< 0.15.10.15.1pip install --upgrade 'pyarrow==0.15.1'
💎RubyGemsred-arrow≥ 0.12.0&&< 0.15.10.15.1bundle update red-arrow --conservative

Affected Products

1 product · 1 configurations
Application
arrowapache
≥ 0.12.0 && ≤ 0.14.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update pyarrow to 0.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12410 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2019-12410 in your dependencies?

Find it across PyPI, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-12410: pyarrow — Fixed in 0.15.1