# CVE-2026-118375: llama.cpp b8841 before b11865 Stack-based Buffer Overflow via ggml-rpc RDMA rdma_recv()


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-118375, GHSA-pmf8-m38j-h768, UBUNTU-CVE-2026-118375

## What is CVE-2026-118375?

CVE-2026-118375 is a critical vulnerability in ggml-org llama.cpp, published on 28 Oct 2026. 

### Official description

llama.cpp b8841 before b11865 contains an out-of-bounds write vulnerability in the ggml-rpc RDMA transport rdma_recv() function that allows unauthenticated peers to overflow the rpc-server stack. Attackers advertising RDMA capabilities in the HELLO message can send up to 256 KiB into a 1-byte stack variable in rpc_serve_client(), crashing the server or potentially executing code.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-118375?


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

No fix has been published for CVE-2026-118375 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118375 being exploited?

There is no known exploitation of CVE-2026-118375 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118375 and fix it if it is affected.

What it is: CVE-2026-118375 is a critical vulnerability in ggml-org llama.cpp, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118375 in the wild and no public exploit code.

Affected product: ggml-org llama.cpp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118375/ (Markdown: https://insights.sbomify.com/CVE-2026-118375/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118375
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118375
- OSV: https://osv.dev/vulnerability/CVE-2026-118375

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118375/
Summaries are generated and may contain mistakes; the official description above is the record.