# OSV-2026-417: Segv on unknown address in arrow::Array::IsNull

> A null pointer dereference in Apache Arrow's Array::IsNull function can cause a segmentation fault, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2026

## What is OSV-2026-417?

OSV-2026-417 is a vulnerability in arrow, published on 18 Mar 2026. 

### Official description

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

```
Crash type: Segv on unknown address
Crash state:
arrow::Array::IsNull
arrow::Status arrow::VisitArrayInline<arrow::ArrayPrinter>
arrow::ArrayPrinter::Print
```

## Which versions are affected by OSV-2026-417?

1 open source package ship an affected version, including arrow.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `arrow` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2026-417?

No fix has been published for OSV-2026-417 yet. Limit exposure of the affected software until one is available.

## Is OSV-2026-417 being exploited?

There is no known exploitation of OSV-2026-417 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2026-417 and fix it if it is affected.

What it is: OSV-2026-417 is a vulnerability in arrow, published on 18 Mar 2026. 
Exploitation: There is no known exploitation of OSV-2026-417 in the wild and no public exploit code.

Affected packages and fixed versions:
- arrow (OSS-Fuzz): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/OSV-2026-417/ (Markdown: https://insights.sbomify.com/OSV-2026-417/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2026-417

---
From sbomify Insights: https://insights.sbomify.com/OSV-2026-417/
Summaries are generated and may contain mistakes; the official description above is the record.