# CVE-2026-78148: ggml-org llama.cpp ggml-RPC Server ggml-rpc.cpp graph_compute null pointer dereference

> Remote attackers can cause a denial of service in the llama.cpp ggml-RPC server via a null pointer dereference in graph_compute.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** 24 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-78148, GHSA-7hmx-m2vh-6qvw, UBUNTU-CVE-2026-78148

## What is CVE-2026-78148?

CVE-2026-78148 is a medium-severity 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 determined in ggml-org llama.cpp bec4772f6. This affects the function rpc_server::graph_compute of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Executing a manipulation can lead to null pointer dereference. The attack may be launched remotely. The pull request to fix this issue awaits acceptance.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-78148 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78148 is a medium-severity 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-78148 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-78148/ (Markdown: https://insights.sbomify.com/CVE-2026-78148/index.md)
```

## Sources

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

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