GHSA-x563-6hqv-26mr
Ibis PyArrow dependency allows arbitrary code execution when loading a malicious data file
Blast Radius
ibis-frameworkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Deserialization of untrusted data in IPC and Parquet readers in PyArrow versions 0.14.0 to 14.0.0 allows arbitrary code execution. An application is vulnerable if it reads Arrow IPC, Feather or Parquet data from untrusted sources (for example user-supplied input files). This vulnerability only affects PyArrow, not other Apache Arrow implementations or bindings.
Note that Ibis itself makes extremely limited use of pyarrow.parquet.read_table:
read_tableis used in tests, where the input file is entirely controlled by the Ibis developersread_tableis used in theibis/examples/__init__.pyas a fallback for backends that don't support reading Parquet directly. Parquet data used inibis.examplesare also managed by the Ibis developers. This Parquet data is generated from CSV files and SQLite databases.- The Pandas and Dask backends both use PyArrow to read Parquet files and are therefore affected.
Ibis does not make use of APIs that directly read from either Arrow IPC files or Feather files.
Patches
Ibis imports the pyarrow_hotfix package wherever pyarrow is used, as of version 7.1.0.
Upgrading to Arrow 14.0.1 is also a possible solution, starting in Ibis 7.1.0.
Workarounds
Install pyarrow_hotfix and run import pyarrow_hotfix ahead of any and all import ibis statements.
For example:
import ibis
becomes
import pyarrow_hotfix
import ibis
References
https://www.cve.org/CVERecord?id=CVE-2023-47248 https://nvd.nist.gov/vuln/detail/CVE-2023-47248
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ibis-framework | all versions | 7.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ibis-framework. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ibis-framework to 7.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x563-6hqv-26mr 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 pinpoints whether GHSA-x563-6hqv-26mr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-x563-6hqv-26mr. 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-x563-6hqv-26mr in your dependencies?
O3 detects GHSA-x563-6hqv-26mr across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.