Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Nuxt Ollama: Public Runtime Config Exposes Ollama API Key to Browser Clients

CVE-2026-59158GHSA-fxg7-897c-57mp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt-ollama 1.3.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-59158: 0.50% estimated exploitation activity in the next 30 days; percentile 43.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Public Runtime Config Exposes Ollama API Key to Browser Clients Summary nuxt-ollama@1.2.26 unconditionally merges all module options — including apikey — into Nuxt's public runtime config (runtimeConfig.public.ollama). Nuxt serializes runtimeConfig.public into the SSR HTML response inside a <script payload block (window.NUXT), making the API key visible in plaintext to any unauthenticated HTTP client that fetches the page. An attacker with no credentials can steal the Ollama cloud API key with a single HTTP GET request, then use it to make arbitrary requests to the Ollama API at the operator's expense. Details The vulnerability is a design flaw in src/module.ts. During Nuxt module setup, the entire options object — which contains apikey when configured for cloud Ollama as documented in README.md:71-80 — is merged into the public runtime config namespace: Nuxt's SSR pipeline serializes runtimeConfig.public and embeds it in every server-rendered HTML page for client-side hydration.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-fxg7-897c-57mp

  2. Revision 2 · amended ·

    Amended from osv record GHSA-fxg7-897c-57mp

  3. Revision 1 · created ·

    Published from ghsa record GHSA-fxg7-897c-57mp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59158

Advisory: Nuxt Ollama: Public Runtime Config Exposes Ollama API Key to Browser Clients
IDs: CVE-2026-59158, GHSA-fxg7-897c-57mp
Record: https://patchnext.com/advisories/cve-2026-59158 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt-ollama 1.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt-ollama: affected >= 1.2.26, < 1.3.1; fixed in 1.3.1

## Suggested inspection (read-only)
- `npm ls nuxt-ollama --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt-ollama.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fxg7-897c-57mp (GitHub-reviewed advisory GHSA-fxg7-897c-57mp lists affected ranges: npm nuxt-ollama >=1.2.26 <1.3.1)
- Verified: https://osv.dev/vulnerability/GHSA-fxg7-897c-57mp (OSV record GHSA-fxg7-897c-57mp lists affected ranges: npm nuxt-ollama >=1.2.26 <1.3.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…