# CVE-2026-78147: ggml-org llama.cpp ggml-RPC Server ggml-rpc.cpp deserialize_tensor deserialization

> Remote attackers can exploit unsafe deserialization in the llama.cpp RPC server to potentially execute arbitrary code.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-78147, GHSA-f4vj-w5xq-5xph, UBUNTU-CVE-2026-78147

## What is CVE-2026-78147?

CVE-2026-78147 is a medium-severity unsafe deserialization vulnerability in ggml-org llama.cpp, published on 23 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in ggml-org llama.cpp bec4772f6. The impacted element is the function deserialize_tensor of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Performing a manipulation of the argument op/op_params results in deserialization. The attack may be initiated remotely. This vulnerability is distinct from CVE-2026-34159 (GHSA-j8rj-fmpv-wcxw, PR #20908), which only added a buffer==nullptr rejection in create_node() and does not validate op or op_params. The reported GitHub issue was closed automatically due to inactivity.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-78147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78147 is a medium-severity unsafe deserialization vulnerability in ggml-org llama.cpp, published on 23 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78147 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-78147/ (Markdown: https://insights.sbomify.com/CVE-2026-78147/index.md)
```

## Sources

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

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