CVE-2026-116467 ggml-org CVE debrief

Who should care

Defenders responsible for ggml-org llama.cpp deployments should assess exposure and verify the affected version. They should also review compensating controls for exposed systems, monitor for potential remote attacks, and track exceptions and retest remediated assets. Security teams and vulnerability management teams should prioritize verifying the affected version and assessing exposure.

Why it matters

Defenders should prioritize verifying the affected version and assessing exposure, as the vulnerability allows for remote attacks and has not been fully addressed by the vendor.

• Verify affected versions and assess exposure to remote attacks
• Monitor for potential vulnerabilities in the Mirostat Sampler component
• Review and update ggml-org llama.cpp deployments to prevent exploitation

Technical summary

The vulnerability is located in the src/llama-sampler.cpp file of the Mirostat Sampler component in ggml-org llama.cpp up to 0.7.0. The manipulation leads to a reachable assertion, allowing for remote attacks. Defenders should prioritize verifying the affected version and assessing exposure, as the vulnerability allows for remote attacks and has not been fully addressed by the vendor. Affected product deployments should be verified, and owners assigned for follow-up. The project was informed of the problem early through a pull request but has not reacted yet.

Defensive priority

Defenders should prioritize verifying the affected version and assessing exposure, as the vulnerability allows for remote attacks.

Recommended defensive actions

• Verify the version of ggml-org llama.cpp and assess exposure
• Review the Mirostat Sampler component for potential vulnerabilities
• Monitor for potential remote attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in ggml-org llama.cpp up to 0.7.0, specifically in the src/llama-sampler.cpp file of the Mirostat Sampler component. However, the vendor's response and affected versions require further verification. Defenders should verify the affected version, assess exposure, and monitor for potential remote attacks. The manipulation leads to a reachable assertion, allowing for remote attacks. Evidence limits suggest verifying ggml-org llama.cpp deployments and reviewing the Mirostat

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.