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

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.

Published: 2025-06-17 Last update: 2025-08-27 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-49847 is rated Moderate Risk (60.1/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.61%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-49847

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-13 0.18% 0.61% +0.43%
2 2026-03-03 0.05% 0.18% +0.13%
3 2025-06-23 0.05%

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-49847

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 [email protected]

Weakness enumeration for CVE-2025-49847

OS Trackers for CVE-2025-49847

vendor priority summary link
debian not yet assigned CVE-2025-49847 not yet assigned priority: Debian including 1 source packages (llama.cpp), 2 status rows across 2 suites (forky, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-49847
ubuntu medium CVE-2025-49847 medium priority: Ubuntu including 1 source packages (llama.cpp), 6 status rows across 6 suites (jammy, noble, oracular, plucky, questing, upstream): DNE 4, needs-triage 2. https://ubuntu.com/security/CVE-2025-49847

Affected software / configurations for CVE-2025-49847

Vendor Product Version Raw CPE
ggml llama.cpp < b5662 cpe:2.3:a:ggml:llama.cpp:*:*:*:*:*:*:*:*

References for CVE-2025-49847

cvelogic Threat Intelligence