CVE-2026-59158: thoda-dev nuxt-ollama advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-27).

Weakness: CWE-522: Insufficiently Protected Credentials

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

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

VEDAS cluster: VEDAS:DOVEYDRIFT

Exploit Observer links 5 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (5)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (4)

Catalogue entries, not exploit evidence.

Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-fxg7-897c-57mp
Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-59158
Vulnerability database or vendor advisory: https://osv.dev/vulnerability/CVE-2026-59158
Vulnerability database or vendor advisory: https://osv.dev/vulnerability/GHSA-fxg7-897c-57mp

2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS: 0.005
low predicted chance of attack
VEDAS: 0.982
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Nuclei · Suricata

Who is affected

Product	Affected	Not affected
thoda-dev nuxt-ollama	version < 1.3.1	Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: npm nuxt-ollama.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

Nuxt Ollama - Public Runtime Config API Key Exposure
Nuxt Ollama before 1.3.1 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. No Ollama request from the template is required for the secret to leak.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /); it decides using dsl matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash

nuclei -u https://your-host -t CVE-2026-59158.yaml

Show the template (39 lines)

yaml

id: CVE-2026-59158

info:
  name: "Nuxt Ollama - Public Runtime Config API Key Exposure"
  author: vedas-arpsyndicate
  severity: high
  description: |
    Nuxt Ollama before 1.3.1 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. No Ollama request from the template is required for
    the secret to leak.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-59158&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=nuxt-ollama&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 7.5
    cve-id: CVE-2026-59158
    cwe-id: CWE-522
  metadata:
    verified: false
    max-request: 1
  tags: cve,cve2026,nuxt-ollama,exposure,disclosure

http:
  - raw:
      - |
        GET / HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - 'contains(body, "__NUXT__")'
          - 'contains(body, "ollama")'
          - 'contains(body, "api_key")'
          - 'status_code == 200'
        condition: and

CVE-2026-59158.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-59158 Nuxt Ollama - Public Runtime Config API Key Exposure. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-59158 Nuxt Ollama - Public Runtime Config API Key Exposure"; flow:established,to_client; file.data; content:"__NUXT__"; nocase; fast_pattern; content:"ollama"; nocase; distance:0; content:"api_key"; nocase; distance:0; classtype:web-application-attack; reference:cve,CVE-2026-59158; reference:url,https://www.exploit.observer/?keyword=CVE-2026-59158&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=nuxt-ollama&match=exact; sid:1093002; rev:1;)

CVE-2026-59158.rules on GitHub

References

Other references

https://github.com/thoda-dev/nuxt-ollama/security/advisories/GHSA-fxg7-897c-57mp (x_refsource_CONFIRM)
https://github.com/thoda-dev/nuxt-ollama/commit/156e813783ef322ee10dbbdd6bf446a449e1a04f (x_refsource_MISC)
https://github.com/thoda-dev/nuxt-ollama/releases/tag/v1.3.1 (x_refsource_MISC)

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.