Medium severity · published Aug 6, 2026
CVE-2026-70639
llama.cpp b1886–b7445 Null Pointer Dereference DoS via llama-android.cpp
5.5
CVSS
0.2%
EPSS
No
On KEV
Description
llama.cpp builds b1886 through b7445 contain a null pointer dereference vulnerability in the LLaMA-Android JNI wrapper where the bench_1model() function fails to validate the model context pointer before dereferencing it. Attackers can supply a malicious, corrupt, or truncated model file to trigger a null context condition, causing a SIGSEGV crash that terminates the Android application process and results in denial of service.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 9% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
LL
llama.cpp · ggml-org
b1886 through b7445; 0.9.0 through 0.17.1 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-70639
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-70639
Patch
https://github.com/Vladimir-tokarev-cyera/llama-cpp-security-patches
Patch
https://github.com/ggml-org/llama.cpp/commit/5c0d18881e0e9794c96b2602736b758bac9d9388
Patch
https://github.com/ggml-org/llama.cpp/releases/tag/b7446
Third Party Advisory
https://www.vulncheck.com/advisories/llama-cpp-b1886-b7445-null-pointer-dereference-dos-via-llama-android-cpp
More from llama.cpp
9.8
CVE-2026-34159
llama.cpp: Unauthenticated RCE via GRAPH_COMPUTE buffer=0 bypass in llama.cpp RPC backend
8.2
CVE-2024-58400
llama.cpp before b3701 Out-of-Bounds Read in llama_decode via Token IDs
8.1
CVE-2026-118375
llama.cpp b8841 before b11865 Stack-based Buffer Overflow via ggml-rpc RDMA rdma_recv()
8.1
CVE-2026-107183
llama.cpp before b11393 Use-After-Free via common_chat_peg_mapper chat_parser
8.1
CVE-2026-43632
llama.cpp b7492–b9060 Use-After-Free in Tokenization Endpoints