Live › vulnerability › CVE-2026-119052
llama.cpp's ggml-rpc server fails to catch an exception when a client sends a message with an oversized length field after the HELLO handshake. An unauthenticated remote attacker can crash the rpc-server process and deny service to every connected client.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 14:25 UTC. All times on this page are UTC.
Teams that run llama.cpp's ggml-rpc server (rpc-server) to share model compute over the network are exposed. Local-only use of llama.cpp without the RPC server is not affected by this flaw as described. Teams that keep the RPC port off untrusted networks have less exposure.
No product ranges from the sources yet.
rpc-server --version or the build tag in your deployment; affected builds are from b2877 up to but not including b11935.b11935 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
llama.cpp b2877 before b11935 contains an uncaught exception vulnerability in the ggml-rpc server that allows unauthenticated remote attackers to crash the rpc-server by sending oversized message lengths. After the HELLO handshake, attackers can send a command such as SET_TENSOR with a length above std::vector::max_size(), triggering an uncaught std::length_error that aborts the process and denies service to all clients.
This page as .md · .json · in your agent: get_signal("CVE-2026-119052")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.