VulnerabilityPublished 27 Oct 2026

CVE-2026-59158: thoda-dev nuxt-ollama · Insufficiently Protected Credentials

Affects thoda-dev nuxt-ollamaSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3.1 soon.

Data as of 27 Oct 2026, 22:57 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.3.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nuxt-ollama and thoda-dev/nuxt-ollama to 1.3.1.

Affected software

Product	Affected	Fixed in
thoda-devnuxt-ollama	Affected <1.3.1	Fixed in 1.3.1
GitHubthoda-dev/nuxt-ollama`pkg:github/thoda-dev/nuxt-ollama`Other threats	Affected <1.3.1	Fixed in 1.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade nuxt-ollama to version 1.3.1 or later, where the issue is fixed by not exposing the cloud api_key in the public runtime configuration.

Description

CVE-2026-59158 is a vulnerability in nuxt-ollama versions prior to 1.3.1 where an API key configured for cloud access is exposed in the client-side HTML payload. This exposure occurs because the module options, including the cloud api_key, are merged into a public runtime configuration that Nuxt serializes into the server-rendered HTML. As a result, unauthenticated clients can retrieve the API key in plaintext, enabling unauthorized use of the cloud API. The issue is fixed in version 1.3.1.

Impact

An attacker can obtain the cloud API key by simply fetching a page from a vulnerable Nuxt application, as the key is exposed in the client-side HTML payload. With the stolen key, unauthorized cloud API requests can be made at the operator's expense, potentially leading to quota or rate-limit exhaustion. If the key grants access to stored models or conversations, those resources may also be compromised. There is no indication of direct code execution or system compromise, but the confidentiality of the API key is severely impacted.

Summary

The nuxt-ollama package integrates the Ollama JavaScript library into Nuxt applications. In versions before 1.3.1, the source code unconditionally merges all module options, including the cloud api_key, into runtimeConfig.public.ollama. Nuxt then serializes this public configuration into the server-rendered HTML window.__NUXT__ payload, exposing the API key to any client fetching the page. Additionally, the exposed key is used as a Bearer token in browser-side Ollama requests. This leads to an insufficient protection of credentials (CWE-522), allowing attackers to steal the API key and make unauthorized cloud API requests, potentially exhausting quotas or accessing stored models and conversations. The vulnerability is addressed in version 1.3.1.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 22:43 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats