VulnerabilityPublished 2 Nov 2026Updated 5 Nov 2026

CVE-2026-111959: Apache Arrow Rust · Improper validation of RunEndEncoded arrays allows out of bounds reads

Affects arrow-dataSource GCVE Database

Compare

Authoritative record:CVE-2026-111959· High

Not known to be exploited · fixed in 60.1.0 : patch arrow-data soon.

Data as of 5 Nov 2026, 09:48 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 60.1.0, 59.3.2, 58.4.1 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade arrow-data to 60.1.0, 59.3.2, 58.4.1 or 57.3.2.

Affected software

Product	Affected	Fixed in
crates.ioarrow-data`pkg:cargo/arrow-data`Other threats	Affected >=33.0.0 <57.3.2 >=58.0.0 <58.4.1 >=59.0.0 <59.3.2 >=60.0.0 <60.1.0	Fixed in 57.3.2 58.4.1 59.3.2 60.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading to versions 57.3.2, 58.4.1, 59.3.2, or 60.1.0 or later. These versions include proper validation to prevent out-of-bounds reads in RunEndEncoded arrays. No other mitigations are indicated.

Description

A vulnerability in Apache Arrow Rust's RunEndEncoded arrays allows out-of-bounds reads due to improper validation of array data. This flaw occurs when reading the last value via certain APIs, potentially exposing memory beyond the intended bounds. The issue has been fixed in versions 57.3.2, 58.4.1, 59.3.2, and 60.1.0 by improving validation of RunEndEncoded array contents.

References

Community reviews

Loading reviews…