ggml-org llama.cpp up to 0.17.1 Recurrent Memory State Restore Path out-of-bounds

Summaryinfo

A vulnerability was found in ggml-org llama.cpp up to 0.17.1. It has been classified as problematic. The impacted element is an unknown function of the component Recurrent Memory State Restore Path. Performing a manipulation results in out-of-bounds. This vulnerability is identified as CVE-2026-43630. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in ggml-org llama.cpp up to 0.17.1. This affects an unknown code block of the component Recurrent Memory State Restore Path. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:

llama.cpp builds b5702 through b7653 contain an out-of-bounds read vulnerability in the recurrent memory state restore path that allows attackers with write access to the slot save directory to read memory past the end of the allocated cells array. Attackers can craft a malicious slot file with an oversized seq_id value to trigger an out-of-bounds read that leaks heap data including pointer values into server logs, defeating ASLR protections and facilitating further exploitation.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-43630 since 05/01/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• ggml-org

Name

• llama.cpp

Version

• 0.17.0
• 0.17.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion