Quick answers
- Is CVE-2026-105839 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105839 being exploited in the wild.
- How severe is CVE-2026-105839?
- High severity, with a CVSS score of 7.8, published 6 October 2026.
- Which products and versions are affected?
- Libmikmod before 3.3.14.
- Is there a fix for CVE-2026-105839?
- Yes: fixed in libmikmod 3.3.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105839 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-105839?
- Check whether you run Libmikmod at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: libmikmod 3.3.14
Technical details
The vulnerability is an integer overflow in the OKT_doPBOD() function within libmikmod's Oktalyzer loader that wraps the 16-bit numtrk (track count) value in the SLEN chunk. This overflow causes subsequent PBOD writes to exceed allocated track pointer bounds, resulting in heap buffer overflow. An attacker can craft a malicious OKT module file that triggers this condition, leading to memory corruption and potential arbitrary code execution.
Affected products
- libmikmod libmikmod before 3.3.14
Timeline
- 2026-10-06: disclosed