ggml-org llama.cpp Vulnerability Disclosed: CVE-2026-116096 Triggers Out-of-Bounds Write Risk
By Mr.Xu Community Post
Published:
Summary:A security vulnerability (CVE-2026-116096) has been identified in ggml-org's llama.cpp, affecting the list_pockettts_state_slots function in the Pocket-TTS component. By manipulating the mmproj argument, an attacker can trigger an out-of-bounds write. Although local access is required for the attack, the exploit code is publicly available and could be used maliciously. Upgrading to version b11796 resolves the issue, but the root cause remains unaddressed.
Vulnerability Overview
A critical security vulnerability (CVE-2026-116096) has been identified in ggml-org's llama.cpp, affecting the list_pockettts_state_slots function in the Pocket-TTS component. The vulnerability stems from improper handling of the mmproj parameter, leading to an out-of-bounds write. This type of vulnerability can be exploited by attackers to execute arbitrary code or corrupt program memory through crafted input.
Technical Details and Impact
- Vulnerability Location: The vulnerability is located in the list_pockettts_state_slots function within the tools/mtmd/models/pockettts-gen.cpp file.
- Attack Conditions: The attack requires local access, meaning the attacker must be able to provide a specially crafted mmproj file to the target system.
- Potential Impact: Although the attack conditions are limited, successful exploitation can lead to arbitrary code execution or program crashes, affecting system stability.
Remediation
ggml-org has released a fix in version b11796, which introduces stricter input validation and boundary checks to address the vulnerability. The patch name is 0a1ef309cdbb9f2024f58a38fb4c42352c5db569. It is recommended that all users upgrade to this version to mitigate the risk.
Root Cause and Future Improvements
While the current version prevents the vulnerability by detecting and aborting malicious input, the root cause has not yet been fully addressed. The ggml-org team is considering more robust input parsing and memory management mechanisms to prevent similar vulnerabilities in the future.
Developer Recommendations
- Upgrade Immediately: All developers using llama.cpp should upgrade to version b11796 as soon as possible.
- Input Validation: Always perform strict validation and boundary checks when handling external inputs.
- Security Audits: It is recommended to conduct a comprehensive security audit of the relevant code to identify other potential vulnerabilities.
Conclusion
This vulnerability disclosure serves as a reminder that security is a critical concern even in open-source projects. Timely updates and strict security practices are key to protecting systems from attacks.
— END —Source: Reddit r/LocalLLaMA (2026-10-26)
Tags: #Security Vulnerability #Open Source Project #Memory Management #ggml-org #AI Security
Editorial & Fact-Checking Note: This article is compiled from primary research, official release documentation, and source papers by the ZICQ Newsroom pipeline with automated entity verification and human editorial review. If you notice any technical inaccuracy, please submit a correction via our corrections policy or email our editorial desk directly.
Community Comments