Loading vulnerability…
CVE-2026-59158 is a high-severity insufficiently protected credentials vulnerability in nuxt-ollama and related packages before version 1.3.1. The module merges configured options, including an Ollama API key, into Nuxt public runtime configuration. That public configuration is serialized into server-side-rendered HTML and is therefore accessible to unauthenticated browser clients. Version 1.3.1 separates the API key from public configuration and retains it in private server-side runtime configuration.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity vulnerability affecting the nuxt-ollama library and related packages. It is scored CVSS 3.0 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and is associated with CWE-522.
A high-severity credentials-exposure vulnerability in npm package nuxt-ollama. Version 1.2.26 places configured Ollama cloud API keys in Nuxt's public runtime configuration, causing them to be serialized into server-rendered HTML and accessible through an unauthenticated HTTP request.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.