Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-59158Published 2026-10-27

CVE-2026-59158 — thoda-dev nuxt-ollama

high

As of 2026-10-27, CVE-2026-59158 is a HIGH-severity vulnerability in thoda-dev nuxt-ollama, CVSS v3.1 7.5, EPSS 0.5% (42.8th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-59158 as of 2026-10-27; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
7.5/10High
EPSS
0.5%Higher than 42.8% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
5.5/10Threadlinqs triage score
Published
CVSS v3.1 7.5 (HIGH) · EPSS 0.5% (higher than 42.8% of all scored CVEs) · Priority 5.5/10 · Published 2026-10-27

Last updated:

What is CVE-2026-59158?

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.

The record classifies CVE-2026-59158 under weakness class CWE-522. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 23 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.5 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (FIRST)
0.5% probability of exploitation in the next 30 days, higher than 42.8% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-27

Is CVE-2026-59158 being exploited?

It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.

Affected products and versions

  • thoda-dev: nuxt-ollama

Affected software packages:

  • npm:nuxt-ollama — patched in 1.3.1

How to fix CVE-2026-59158

Fixed versions are recorded for 1 package: npm:nuxt-ollama 1.3.1. No vendor patch reference has been recorded for CVE-2026-59158 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-59158

No threat campaign in the Threadlinqs corpus currently references CVE-2026-59158, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references