GPU VulnDB

Database/AI/ML frameworks & serving

llama.cpp: reachable assertion in the Mirostat sampler aborts the server remotely

CVSS 6.9CVE-2026-116467AI/ML frameworks & servingcurated

Impact

A remote request can drive the Mirostat sampler into a reachable assertion, aborting the process. Where llama.cpp is exposed as a server, that is an unauthenticated kill of the serving replica, and because the model has to be reloaded into GPU memory on restart, recovery is a cold start affecting everyone on that replica rather than a single failed request. The record is thin: it comes from a third-party database, names only the sampler and the file, and gives no reproduction detail or exploit mechanism, and the only impact claimed is low availability.

Who can reach it

Remote and unauthenticated per the record - a request to a llama.cpp server that reaches Mirostat sampling. The record does not say which parameter values are required.

What to do

No upstream fix as of this record: the project was notified through pull request 29992 and had not acted. Mitigate by disabling Mirostat sampling where you can pin sampler settings server-side, rejecting client-supplied Mirostat parameters at the gateway, and keeping a supervisor in place to restart the process. Track the pull request for a fix; no fixed version exists to name.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.