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

High 7.5 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-59158?

CVE-2026-59158 is a high-severity vulnerability in thoda-dev nuxt-ollama, published on 27 Oct 2026.

Official 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.

Weakness: CWE-522

Which versions are affected by CVE-2026-59158?

2 open source packages ship an affected version, including nuxt-ollama.

PackageAffectedFixed in
nuxt-ollama npmFrom 1.2.261.3.1
nuxt-ollama npmFrom 1.2.261.3.1

How do I fix CVE-2026-59158?

Upgrade nuxt-ollama to 1.3.1 or later.

Is CVE-2026-59158 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59158 exists.

Sources

Also known as GHSA-fxg7-897c-57mp.

Is CVE-2026-59158 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free