llama.cpp (RPC backend): Unsafe `data` pointer in `rpc_tensor`

Impact

Unsafe data pointer in rpc_tensor → arbitrary address write

Who can reach it

Unauthenticated network to the llama.cpp RPC port on a distributed inference setup

What to do

Rebuild; the RPC backend has no authentication and must never be tenant-reachable

References

Related entries

• llama.cpp (RPC backend): Arbitrary address read via `rpc_tensor.data`CVE-2024-42478 · llama.cpp (RPC backend)Medium
• MLflow (`extract_archive_to_dir`): Path traversal in the dbconnect artifact cacheCVE-2025-15036 · MLflow (`extract_archive_to_dir`)Critical
• vLLM (Mooncake ZMQ/TCP): Unsafe deserialization exposed on all interfacesCVE-2025-32444 · vLLM (Mooncake ZMQ/TCP)Critical
• ChromaDB: Pre-authentication code injectionCVE-2026-45829 · ChromaDBCritical
• Kubeflow Pipelines frontend: unauthenticated SSRF proxy reaches cloud metadata and cluster-internal APIsCVE-2026-54745 · Kubeflow Pipelines frontend (/_proxy/ route in proxy-middleware.ts)Critical
• Xinference: unauthenticated chat request reaches eval() in the Llama3 tool-call parserCVE-2026-61539 · Xinference (Llama3 tool-call parser, `_eval_llama3_chat_arguments`)Critical