# CVE-2026-92786: LightGBM through 4.7.0 Out-of-Bounds Write via Crafted Model

> Attackers can achieve arbitrary code execution or denial of service by crafting malicious model files that trigger out-of-bounds writes in LightGBM.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-fhjh-xqqj-cjf5

## What is CVE-2026-92786?

CVE-2026-92786 is a high-severity memory corruption vulnerability in lightgbm-org LightGBM, published on 16 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

LightGBM through 4.7.0 fails to validate child and split array values when parsing text models, allowing attackers to write out-of-bounds memory during SHAP prediction. Attackers can craft malicious model files with invalid node references that trigger out-of-bounds writes at attacker-chosen offsets in the leaf_depth_ buffer during feature contribution computation.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-92786?


## How do I fix CVE-2026-92786?

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

## Is CVE-2026-92786 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92786 and fix it if it is affected.

What it is: CVE-2026-92786 is a high-severity memory corruption vulnerability in lightgbm-org LightGBM, published on 16 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92786 in the wild and no public exploit code.

Affected product: lightgbm-org LightGBM. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-92786/ (Markdown: https://insights.sbomify.com/CVE-2026-92786/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92786
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92786
- OSV: https://osv.dev/vulnerability/CVE-2026-92786

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