Live › vulnerability › CVE-2026-118375
Go to dashboardllama.cpp's ggml-rpc RDMA transport writes up to 256 KiB into a 1-byte stack variable in the RPC server. An unauthenticated peer that advertises RDMA in its HELLO message can crash the server or potentially execute code.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 03:31 UTC. All times on this page are UTC.
Teams running llama.cpp's ggml-rpc RPC server with the RDMA transport, where peers can reach the server over the network. Systems that only run llama.cpp locally, or that do not run the RPC server, are not exposed by this flaw.
No product ranges from the sources yet.
llama-server --version or check the build tag of the llama.cpp binary; affected builds are from b8841 up to but not including b11865.rpc-server) is running with RDMA support enabled and reachable from untrusted networks.b11865 or later.rpc-server port to untrusted networks or disable RDMA transport.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
llama.cpp b8841 before b11865 contains an out-of-bounds write vulnerability in the ggml-rpc RDMA transport rdma_recv() function that allows unauthenticated peers to overflow the rpc-server stack. Attackers advertising RDMA capabilities in the HELLO message can send up to 256 KiB into a 1-byte stack variable in rpc_serve_client(), crashing the server or potentially executing code.
This page as .md · .json · in your agent: get_signal("CVE-2026-118375")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.