CVE-2024-43598 json
LightGBM Remote Code Execution Vulnerability
published last yr. modified 8d ago also GHSA-2586-f3p4-hq84 , PYSEC-2024-231 , EUVD-2024-40349
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
LightGBM Remote Code Execution Vulnerability
Patch / fix
- pypi lightgbm 4.6.0
- Microsoft LightGBM 4.6.0
Is CVE-2024-43598 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | lightgbm | >=1.0.0, <4.6.0 <4.6.0 |
4.6.0 |
Affected products
- Microsoft LightGBM
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-43598
vendor-advisory, web, patch, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-43598
advisory
-
github.com
/microsoft/LightGBM
package
-
github.com
/pypa/advisory-database/tree/main/vulns/lightgbm/PYSEC-2024-231.yaml
web
-
github.com
/advisories/GHSA-2586-f3p4-hq84
advisory
Sources
- CVE List CVE-2024-43598
- GitHub Advisory GHSA-2586-f3p4-hq84
- NVD CVE-2024-43598
- OSV PYSEC-2024-231
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.