CVE-2026-59158: nuxt-ollama puts your Ollama cloud API key in every server-rendered page, upgrade to 1.3.1
The nuxt-ollama module copied all its options, including a configured Ollama cloud api_key, into Nuxt's public runtime config before 1.3.1. Nuxt embeds that config in the window.__NUXT__ payload of every server-rendered page, so anyone who loads a page can read the key and spend your Ollama quota.
What it is
src/module.ts merges every module option into runtimeConfig.public.ollama, including api_key when you follow the documented cloud setup.
Nuxt serializes runtimeConfig.public into the HTML it sends to browsers, so the key appears in plain text in the window.__NUXT__ script block. The page doesn't even need to make an Ollama request.
The browser-side useOllama composable also sends the key as an Authorization Bearer header.
A stolen key allows Ollama API requests at your expense, can exhaust your quota or rate limits, and may expose stored models or conversations if the key allows it.
How to check
- Check whether your Nuxt app uses nuxt-ollama before 1.3.1 with an api_key set.
- Open your site's page source and search for api_key or your key inside window.__NUXT__.
How to fix
- Upgrade nuxt-ollama to 1.3.1 or later.
- Rotate the Ollama API key, because any key that was served in your pages should be treated as leaked.
npm install nuxt-ollama@^1.3.1
# check a live page for the leak
curl -s https://your-site.example/ | grep -o 'api_key:"[^"]*"'Sources
- criticalCVE-2026-103663: Ollama /api/pull path traversal can lead to code execution as root
- criticalCVE-2026-61732: web pages can forge operator turns in the Decepticon hacking agent with ChatML tokens and run commands, upgrade to 1.1.17
- criticalCVE-2025-63389: Ollama Platform has missing authentication enabling attackers to perform model management operations
- highCVE-2026-102697: Ollama agent mode's Bash approval can be bypassed with ; or &&