Live › vulnerability › CVE-2026-59158
Go to dashboardThe nuxt-ollama module copies its configured cloud api_key into the public runtime config, which Nuxt serializes into the server-rendered HTML window.__NUXT__ payload. Any visitor who loads a page can read the key in plaintext and use it for unauthorized Ollama cloud requests, spending quota or reading stored models and conversations the key can access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 23:29 UTC. All times on this page are UTC.
Nuxt applications that use the nuxt-ollama module with a cloud api_key configured are exposed, because the key is merged into the public runtime config and shipped to every client in the page payload. Teams running a local Ollama server without a cloud key, or on nuxt-ollama 1.3.1 or later, are not affected by this flaw.
No product ranges from the sources yet.
npm ls nuxt-ollama (or the matching lockfile entry).grep -rn "api_key" nuxt.config.*.window.__NUXT__ containing an ollama block with api_key.1.3.1 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-59158")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.