Memory corruption via unchecked model node indices
Published Sep 16, 2026 · Updated Sep 21, 2026
Out-of-bounds write in LightGBM 4.7.0 and earlier allows attackers to corrupt process memory via a crafted text model. The text parser checks left_child and right_child array lengths but not their values, and RecomputeLeafDepths bit-inverts an invalid child value into an unchecked leaf_depth_ write index. Exploitation requires a user or process to load the untrusted model and request SHAP feature contributions; code execution has not been demonstrated.
Summary
What happened
Out-of-bounds write in LightGBM 4.7.0 and earlier allows attackers to corrupt process memory via a crafted text model. The text parser checks left_child and right_child array lengths but not their values, and RecomputeLeafDepths bit-inverts an invalid child value into an unchecked leaf_depth_ write index. Exploitation requires a user or process to load the untrusted model and request SHAP feature contributions; code execution has not been demonstrated.
The record
- CVE
- CVE-2026-92786
- Published
- Sep 16, 2026
- Updated
- Sep 21, 2026
- Vendor
- Microsoft Corporation
- Product
- LightGBM
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.7.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started