# CVE-2026-43631: CVE-2026-43631: Unauthenticated RCE in llama-server When Idle Sleep Is Enabled (CVSS 9.2)

> CVE-2026-43631 is a critical-severity remote code execution issue (CVSS 9.2) in llama.cpp builds b, an AI agent. Affected: llama.cpp builds b7492 to b9060 with --sleep-idle-seconds enabled.

- **Canonical URL:** https://catalog.anomity.ai/vuln/cve-2026-43631
- **Aliases:** ti-082, GHSA-6hc7-9rph-cm99
- **Severity:** critical
- **CVSS:** 9.2
- **Attack type:** Remote code execution
- **Component:** llama.cpp builds b (AI agent)
- **Exploited in the wild:** no known exploitation
- **Published:** 2026-08-07
- **Last verified:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/vuln/cve-2026-43631

## Summary

A use-after-free on the vocab pointer in llama.cpp's llama-server lets an unauthenticated remote attacker run code by sending requests while the server is transitioning into sleep mode, a window in which concurrent worker threads dereference memory that has already been freed and that the attacker can reclaim with data of their own. It affects builds b7492 through b9060 and needs the --sleep-idle-seconds feature active, a flag commonly set on exactly the shared internal inference hosts that see the most sensitive prompts. Local inference also changes the exposure shape: these servers are usually stood up by a team rather than provisioned by IT, and frequently listen on the internal network with nothing authenticating in front of them.

## Affected versions

| Affected | Fixed in |
| --- | --- |
| llama.cpp builds b7492 to b9060 with --sleep-idle-seconds enabled | no fixed version listed |

## Am I affected by CVE-2026-43631?

You are affected if you run llama.cpp builds b7492 to b9060 with --sleep-idle-seconds enabled.

## How do I fix CVE-2026-43631?

Update llama.cpp past b9060, or disable --sleep-idle-seconds as an immediate workaround. Then go and find the instances: local inference servers are typically stood up by a team rather than provisioned centrally, so inventory which machines run llama-server, check whether any is listening on a non-loopback interface, and put authentication and network policy in front of the ones that are.

## How do I find every machine running llama.cpp builds b?

Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run llama.cpp builds b and which version, then enforce a policy on it.

## References

- advisory: https://github.com/advisories/GHSA-6hc7-9rph-cm99
- cve: https://nvd.nist.gov/vuln/detail/CVE-2026-43631

## Related vulnerabilities

- [CVE-2026-115726](https://catalog.anomity.ai/vuln/cve-2026-115726) — high
- [manus-one-email-with-a-jsfuck-payload-or-one-shared-project-instruction](https://catalog.anomity.ai/vuln/manus-one-email-with-a-jsfuck-payload-or-one-shared-project-instruction) — high
- [GHSA-632h-h47v-g4x4](https://catalog.anomity.ai/vuln/ghsa-632h-h47v-g4x4) — high
- [plugin4shell-sha-pinning-bypass-gives-zero-click-rce-across-claude-code](https://catalog.anomity.ai/vuln/plugin4shell-sha-pinning-bypass-gives-zero-click-rce-across-claude-code) — critical
- [openai-codex-two-sandbox-escapes-apply-patch-overpatch-in-codex-cli-and](https://catalog.anomity.ai/vuln/openai-codex-two-sandbox-escapes-apply-patch-overpatch-in-codex-cli-and) — high
- [CVE-2026-82533](https://catalog.anomity.ai/vuln/cve-2026-82533) — critical

---

Source: Anomity Security Database (https://catalog.anomity.ai/vuln). Detect affected AI tools on developer devices: https://anomity.ai/?utm_source=catalog&utm_medium=vuln-md&utm_campaign=cve-2026-43631