Nuxt Ollama exposes configured cloud API key in public runtime config
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-522.
Summary
Nuxt Ollama versions before 1.3.1 merge a configured cloud API key into the public runtime configuration. Nuxt serializes that configuration into server-rendered HTML, so the key appears in plaintext (CWE-522). An unauthenticated remote attacker who fetches a page can read the key and make cloud API requests at the operator's expense.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| thoda-dev | nuxt-ollama | before 1.3.1 | 1.3.1 | Patch available | CNA |
| — | nuxt-ollama (npm) | 1.2.26 to before 1.3.1 | 1.3.1 | Patch available | GHSA-fxg7-897c-57mp |
- nuxt-ollama Vendorthoda-dev Affected before 1.3.1 Fixed in 1.3.1 Patch available CNA
- nuxt-ollama (npm) Vendor— Affected 1.2.26 to before 1.3.1 Fixed in 1.3.1 Patch available GHSA-fxg7-897c-57mp
Remediation
Update the npm package nuxt-ollama to version 1.3.1. The sources list no fixed version for thoda-dev nuxt-ollama.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA nuxt-ollama (thoda-dev) Fixed in 1.3.1
- Fix · GHSA-fxg7-897c-57mp nuxt-ollama (npm) Fixed in 1.3.1 Advisory →
Timeline
- 2026-10-27 Threatist record created from CVE-2026-59158
- 2026-10-28 Priority changed: MEDIUM → LOW
- 2026-10-29 CISA SSVC decision points changed
- 2026-10-29 Priority changed: LOW → HIGH
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences