CVE-2026-111959

waiting for further signalsZero needs more public information before it can validate it.
no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Arrow Rust >= 60.0.0, < 60.1.0; >= 59.0.0, <= 59.3.1; >= 58.0.0, <= 58.4.0; >= 33.0.0, <= 57.3.1
fixed in 60.1.0
CWE-125 Out-of-bounds Read
ETK-2026-3281Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 41msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h22m
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Arrow Rust's arrow crate improperly validates RunEndEncoded arrays supplied through the ArrayData interface. An attacker able to provide such array data may cause reads beyond the associated child values array.

mitigation

Update the arrow crate to version 60.1.0 or later. Ensure applications do not accept untrusted array data until the dependency is updated.

fixed in 60.1.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 13:34Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-02 13:34Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-111959

{
  "etk_id": "ETK-2026-3281",
  "cve_id": "CVE-2026-111959",
  "display_id": "CVE-2026-111959",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in Apache Arrow Rust arrays",
  "summary": "Apache Arrow Rust's `arrow` crate improperly validates RunEndEncoded arrays supplied through the ArrayData interface. An attacker able to provide such array data may cause reads beyond the associated child values array.",
  "mitigation": "Update the `arrow` crate to version 60.1.0 or later. Ensure applications do not accept untrusted array data until the dependency is updated.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Arrow Rust",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 60.0.0, < 60.1.0",
        ">= 59.0.0, <= 59.3.1",
        ">= 58.0.0, <= 58.4.0",
        ">= 33.0.0, <= 57.3.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "60.1.0"
      ],
      "package_name": "arrow",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.943309933333333,
  "t0_at": "2026-11-02T13:34:17.835000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T13:34:17.835000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T13:34:17.835000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111959"
    }
  }
}

published 2026-11-02 13:41Z
last change 2026-11-02 15:07Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.