WhisperX tag archive

#Ollama

This page collects WhisperX intelligence signals tagged #Ollama. It is designed for humans, search engines, and AI agents: each item links to a canonical source-backed record with sector, source, timestamp, credibility, and exportable structured data.

Latest Signals (4)

The Lab · 2026-04-06 10:27:09 · GitHub Issues

1. Ollama Embedding Client Exposes SSRF Risk via Unvalidated OLLAMA_URL Environment Variable

A medium-severity SSRF vulnerability has been identified in the Ollama embedding client, allowing potential internal network probing if the environment variable is maliciously configured. The flaw resides in the `src/infrastructure/embeddings/ollama.ts` file, where the `OLLAMA_URL` environment variable is used directly...

The Lab · 2026-05-09 04:31:37 · r/netsec

2. Ollama AI Platform Exposed by Critical Unauthenticated Memory Leak Vulnerability (CVE-2026–7482)

A critical unauthenticated memory leak vulnerability has been disclosed in Ollama, the widely-deployed open-source platform for running large language models locally. Tracked as CVE-2026–7482 and dubbed "Bleeding Llama," the flaw allows attackers to extract sensitive data from system memory without any authentication, ...

The Lab · 2026-05-10 15:01:45 · The Hacker News Echo RSS

3. Critical Ollama Flaw 'Bleeding Llama' Exposes Process Memory on 300,000+ Servers

A critical security vulnerability in Ollama could allow remote, unauthenticated attackers to leak the entire process memory of affected servers, according to researchers at Cyera. The out-of-bounds read flaw, tracked as CVE-2026-7482, carries a CVSS severity score of 9.1 and has been codenamed "Bleeding Llama." With an...

The Vault · 2026-05-12 01:48:26 · GitHub Issues

4. NemoClaw Fixes Critical Re-onboarding Bug: Ollama Loopback Override Skipped on Existing Installations

A critical configuration flaw in NemoClaw left pre-existing Ollama instances bound to all network interfaces, despite displaying a deceptive success message. The bug, now patched in commit addressing issue #3342, caused systems that re-onboarded after an older NemoClaw installation to silently remain exposed to remote ...