llama.cpp: Llama.cpp builds b7492 through the latest b9060 contains a use-after-free vulnerability in the…
llama.cpp
More for llama.cpp RSS feed for llama.cpp
- Severity
- High, CVSS 8.1
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Record
- CVE-2026-43631
- Affects
- llama.cpp
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 6, 2026
- Source last modified
- October 23, 2026
Description
llama.cpp builds b7492 through the latest b9060 contains a use-after-free vulnerability in the vocab pointer of llama-server when the --sleep-idle-seconds feature is enabled, allowing unauthenticated remote attackers to execute arbitrary code. Attackers can trigger the vulnerability by sending requests to affected endpoints while the server transitions to sleep mode, causing concurrent worker threads to dereference a freed vocab pointer that can be reclaimed with attacker-controlled data to achieve remote code execution.
Description quoted from the NVD record.
Who is affected
llama.cpp, made by ggml, is a program that runs AI language models on your own computers so other software can use them. This flaw affects builds b7492 through b9060, the latest build available. It is in the server program that comes with llama.cpp and only matters when its option to go to sleep after a period of no activity is turned on. An attacker who does not need to log in could send requests over the network while the server is going to sleep and run their own code on that machine. This flaw is rated High.
What to do
- If someone on your staff installed or runs llama.cpp, ask them to act on this advisory. If an IT provider or vendor runs it for your organization, send them this advisory and ask when the update will be done.
- Find out whether the server program that comes with llama.cpp is in use and whether its option to sleep after a period of no activity is turned on. This flaw only affects setups with that option turned on.
- No fixed version is named for this flaw yet, so check the vendor advisory linked on this page for a fixed release.
- When a fixed release is available, install it on every machine running the server program.
Analysis written from the source record as of October 23, 2026 and reviewed before publishing.