CVE-2026-116096
MEDIUMDescription
A weakness has been identified in ggml-org llama.cpp. Affected by this issue is the function list_pockettts_state_slots of the file tools/mtmd/models/pockettts-gen.cpp of the component Pocket-TTS. This manipulation of the argument mmproj causes out-of-bounds write. The attack requires local access. The exploit has been made available to the public and could be used for attacks. Upgrading to version b11796 can resolve this issue. Patch name: 0a1ef309cdbb9f2024f58a38fb4c42352c5db569. The affected component should be upgraded. The reported heap out‑of‑bounds write (gen‑audio / pocket‑tts state_out path) is no longer a silent exploitable heap write on current master and the latest release b11871 - a malicious mmproj that previously triggered it now trips a release‑active GGML_ASSERT and aborts. But the submitter's recommended by‑construction fix (PR #29360 "prevent OOB accesses from malformed mmproj files") is still open. So the root cause is detected‑and‑aborted, not prevented‑by‑design.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-119 (Buffer Overflow) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-4966 | Critical | 9.4 | 100% | KEV + Ransom | Fix |
| CVE-2017-11882 | High | 7.8 | 100% | KEV + Ransom | - |
| CVE-2020-0796 | Critical | 10.0 | 100% | KEV + Ransom | - |
| CVE-2008-4250 | Critical | 9.8 | 99% | KEV | - |
| CVE-2017-15944 | Critical | 9.8 | 98% | KEV | Fix |
| CVE-2015-0014 | High | 10.0 | 97% | - | - |
Common questions
How do I fix CVE-2026-116096?
No published fix for CVE-2026-116096 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-116096 being actively exploited?
Not that we know of. CVE-2026-116096 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2026-116096?
CVE-2026-116096 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-116096
Markdown
[](https://tridentstack.com/cve/CVE-2026-116096)HTML
<a href="https://tridentstack.com/cve/CVE-2026-116096"><img src="https://tridentstack.com/cve/badge/CVE-2026-116096.svg" alt="CVE-2026-116096"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-26.