Ollama on Windows — Setup, CORS Fix & Custom Models
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is an instruction-only Ollama setup guide, but it recommends a permanent wildcard CORS setting that can expose the local Ollama service to any website without explaining the risk.
Before following this guide, avoid setting `OLLAMA_ORIGINS=*` permanently unless you fully understand the exposure. Prefer allowing only the exact web app origin you need, and remove or narrow the environment variable when it is no longer required.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A malicious or untrusted website visited in the same browser environment may be able to send requests to the user's local Ollama service if it is running.
Setting Ollama's allowed CORS origins to a wildcard permits browser requests from any origin instead of limiting access to a trusted local web app or specific domain.
Variable name: `OLLAMA_ORIGINS` 4. Variable value: `*` 5. Restart Ollama
Use specific trusted origins instead of `*` where possible, such as the exact localhost port or web-app domain, and avoid making the setting permanent unless needed.
Users may apply the most permissive setting without understanding that narrower origin settings are usually safer.
The wording frames the broad CORS change as required for web apps but does not distinguish between safer scoped origins and the broader wildcard configuration.
## CORS Fix (Required for Web Apps) Web-based AI interfaces need CORS headers. Set this environment variable:
Document the security tradeoff and provide a scoped example before recommending wildcard CORS.