# CVE-2025-53630: Integer Overflow in GGUF Parser can lead to Heap Out-of-Bounds Read/Write in gguf

> An integer overflow in the GGUF parser allows heap out-of-bounds read/write, potentially leading to code execution or crashes in llama.cpp.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2025
- **Updated:** 10 Jul 2025
- **Also known as:** DEBIAN-CVE-2025-53630, GHSA-vgg9-87g3-85w8, UBUNTU-CVE-2025-53630, openSUSE-SU-2025:15343-1

## What is CVE-2025-53630?

CVE-2025-53630 is a high-severity vulnerability in ggml-org llama.cpp, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

llama.cpp is an inference of several LLM models in C/C++. Integer Overflow in the gguf_init_from_file_impl function in ggml/src/gguf.cpp can lead to Heap Out-of-Bounds Read/Write. This vulnerability is fixed in commit 26a48ad699d50b6268900062661bd22f3e792579.

Weakness: CWE-680 (Integer Overflow to Buffer Overflow), CWE-122 (Heap-based Buffer Overflow)

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


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

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

Apply the vendor's patch.

## Is CVE-2025-53630 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53630 is a high-severity vulnerability in ggml-org llama.cpp, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53630 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-53630/ (Markdown: https://insights.sbomify.com/CVE-2025-53630/index.md)
```

## Sources

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

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