CVE-2026-59158
Nuxt Ollama integrates the official Ollama JavaScript library into …
Nuxt Ollama integrates the official Ollama JavaScript library into Nuxt applications. Prior to 1.3.1, `src/module.ts` unconditionally merges all module options, including a configured cloud `api_key`, into `runtimeConfig.public.ollama`. Nuxt serializes this public configuration into the server-rendered HTML `window.__NUXT__` payload, exposing the API key in plaintext to any unauthenticated client that fetches a page. `src/runtime/composables/useOllama.ts` also reads the public key and sends it as an `Authorization` `Bearer` credential in browser-side Ollama requests. Following the documented cloud configuration is sufficient; the visible application template need not make an Ollama request for the secret to leak. A stolen key permits unauthorized cloud API requests at the operator's expense, quota or rate-limit exhaustion, and access to stored models or conversations if the key grants those permissions. This issue is fixed in version 1.3.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/thoda-dev/nuxt-ollama/security/advisories/GHSA-fxg7-897c-57mp
- github.com/advisories/GHSA-fxg7-897c-57mp
- github.com/thoda-dev/nuxt-ollama/commit/156e813783ef322ee10dbbdd6bf446a449e1a04f
- github.com/thoda-dev/nuxt-ollama/releases/tag/v1.3.1
- nvd.nist.gov/vuln/detail/CVE-2026-59158
- cve.org/CVERecord?id=CVE-2026-59158
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.