# CVE-2025-49847: llama.cpp Vulnerable to Buffer Overflow via Malicious GGUF Model

> An attacker can achieve arbitrary code execution by supplying a malicious GGUF model that triggers a buffer overflow in llama.cpp's vocabulary loading.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Jun 2025
- **Updated:** 18 Jun 2025
- **Also known as:** DEBIAN-CVE-2025-49847, GHSA-8wwf-w4qm-gpqr, UBUNTU-CVE-2025-49847, openSUSE-SU-2025:15245-1

## What is CVE-2025-49847?

CVE-2025-49847 is a high-severity memory corruption vulnerability in ggml-org llama.cpp, published on 17 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

llama.cpp is an inference of several LLM models in C/C++. Prior to version b5662, an attacker‐supplied GGUF model vocabulary can trigger a buffer overflow in llama.cpp’s vocabulary‐loading code. Specifically, the helper _try_copy in llama.cpp/src/vocab.cpp: llama_vocab::impl::token_to_piece() casts a very large size_t token length into an int32_t, causing the length check (if (length < (int32_t)size)) to be bypassed. As a result, memcpy is still called with that oversized size, letting a malicious model overwrite memory beyond the intended buffer. This can lead to arbitrary memory corruption and potential code execution. This issue has been patched in version b5662.

Weakness: CWE-195 (Signed to Unsigned Conversion Error), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-49847?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `llamacpp` | openSUSE:Tumbleweed | All versions | 5699-1.1 |

Products: Ggml Llama.cpp.

## How do I fix CVE-2025-49847?

Upgrade to a fixed version.

## Is CVE-2025-49847 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49847 exists.

## Other vulnerabilities in ggml-org llama.cpp

- [CVE-2024-42479](https://insights.sbomify.com/CVE-2024-42479/): llama.cpp allows write-what-where in rpc_server::set_tensor (critical 10.0)
- [CVE-2026-34159](https://insights.sbomify.com/CVE-2026-34159/): llama.cpp: Unauthenticated RCE via GRAPH_COMPUTE buffer=0 bypass in llama.cpp RPC backend (critical 9.8)
- [CVE-2026-43629](https://insights.sbomify.com/CVE-2026-43629/): llama.cpp b4882–b9058 Buffer Overflow in KV Cache State Restore (critical 9.2)
- [CVE-2026-43631](https://insights.sbomify.com/CVE-2026-43631/): llama.cpp b7492–b9060 Use-After-Free RCE via llama-server (critical 9.2)
- [CVE-2026-43632](https://insights.sbomify.com/CVE-2026-43632/): llama.cpp b7492–b9060 Use-After-Free in Tokenization Endpoints (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49847 and fix it if it is affected.

What it is: CVE-2025-49847 is a high-severity memory corruption vulnerability in ggml-org llama.cpp, published on 17 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49847 exists.

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-2025-49847/ (Markdown: https://insights.sbomify.com/CVE-2025-49847/index.md)
```

## Sources

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

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