CVE-2026-59158

Nuxt Ollama: public runtime configuration discloses the configured cloud API key

Published Oct 27, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in the Nuxt Ollama module causes the cloud API key configured in the module options to be merged into the public runtime configuration. Nuxt serializes this public configuration into the HTML payload, exposing the key to any client that fetches a page. The exposed key can be used to send unauthorized requests to the Ollama cloud, potentially exhausting the operator’s quota, incurring costs, or accessing stored models and conversations that the key authorizes. The weakness is a classic case of Sensitive Data Exposure (CWE‑522).

Affected Systems

The issue affects installations of the Nuxt Ollama module by thoda-dev, specifically versions earlier than 1.3.1. Users running those releases should verify the module version and ensure that the secured configuration is not available in the production environment.

Risk and Exploitability

With a CVSS score of 7.5, the vulnerability is considered high. The exploitation surface is broad: any unauthenticated client can retrieve the HTML payload and read the plaintext key. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, but the public nature of the leak makes it highly probable that attackers could simply fetch a page and capture the key. Once obtained, the key enables direct use of the Ollama Cloud API in client‑side requests, potentially causing functional outages or financial impacts.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the nuxt-ollama module to version 1.3.1 or later, which removes the public exposure of the cloud API key
  • Reconfigure the module to store the api_key in runtimeConfig.private instead of public, ensuring it is never exposed in the client‑side payload
  • If an immediate upgrade is not possible, remove any use of the api_key from the public runtime configuration or mask it before serialization, limiting exposure to internal components only

Generated by OpenCVE AI on October 27, 2026 at 23:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-fxg7-897c-57mp Nuxt Ollama: Public Runtime Config Exposes Ollama API Key to Browser Clients
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Thoda-dev
Thoda-dev nuxt-ollama
Vendors & Products Thoda-dev
Thoda-dev nuxt-ollama
Type Values Removed Values Added
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.
Title Nuxt Ollama: public runtime configuration discloses the configured cloud API key
Weaknesses CWE-522
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-522

    Insufficiently Protected Credentials

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 6:23 PM
Reserved
Jul 2, 2026, 4:50 PM
Status
Deferred
Published
Oct 27, 2026, 11:17 PM
Modified
Oct 29, 2026, 7:17 PM