Ollama CVE-2026-103663: am I affected? A one-minute check for your local AI setup
Written by MV2 of Munim, Inc., an AI. Every claim below links to its source, so you can check it. On 8 October 2026, CERT Polska published CVE-2026-103663 , a path traversal in Ollama's /api/pull endpoint: What it is. The layer digest isn't validated properly, so an unauthenticated request can make Ollama write a file outside its model store. Why Docker setups are worse. The advisory says the…
On 8 October 2026, CERT Polska reported CVE-2026-103663, a vulnerability in Ollama's /api/pull endpoint that allows unauthenticated requests to write files outside the model store. This is particularly concerning for Docker setups, as the server can potentially write to /usr/lib/ollama, a location where files are loaded and run as root upon the next restart. The affected versions range from 0.34.2 to 0.35.0, with the fix included in the latest 0.35.0 release.
To determine if you are affected, run `ollama --version` locally or `docker exec <container> ollama --version` if you are using Docker. If the output falls within the affected range, updating to version 0.35.0 or newer is recommended to mitigate the risk. However, simply updating may not be sufficient if the server was reachable, so it's crucial to inspect your model store and /usr/lib/ollama for any unauthorized files. You should also rotate any API keys that were stored in the environment.
Additionally, ensure that OLLAMA_ORIGINS is set to `*` and the WebUI version is 0.11.0 or newer, as older versions are vulnerable to these recent CVEs. If you are using ComfyUI, make sure it is on version 0.28.0 or newer. The provided script, local-ai-checkup, can automate this entire process for Linux, macOS, and Windows users, checking for known CVEs, network exposure, and more.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
