Critical "Bleeding Llama" Vulnerability in Ollama — Memory Exposure Without Authentication

A critical vulnerability that exposes memory contents without authentication has been discovered in **Ollama**, a widely used platform for running LLMs locally. Reported as "Bleeding Llama" on Reddit's r/LocalLLaMA, the issue is a security risk that users running LLMs locally cannot afford to ignore.

Because Ollama runs locally, it's easy to assume that network-based attacks are irrelevant. In reality, however, if the API endpoint is running in a configuration that allows external access, an attacker may be able to retrieve memory contents. Concerns have been raised about the risk of leaking prompt data loaded into memory during LLM inference, as well as sensitive information contained in the context.

With security settings often neglected in favor of local LLM convenience, this discovery may well serve as a wake-up call to rethink the assumption that "local = safe." Ollama users are advised to update to the latest version and review their access restrictions promptly.

Google Is Developing AI Agent "Remy" — Business Insider Reports

**Business Insider** has reported that Google is developing a new AI agent called "Remy." Remy is positioned as an extension of the Gemini assistant and is seen as a centerpiece of Google's AI agent strategy.

According to the report, Remy is designed as an agent that autonomously executes tasks, going beyond the chatbot-style interactions of today. While Google has built up a portfolio of AI products centered on Gemini, some have pointed out that it lags behind competitors in the autonomous agent space — Remy could play a role in closing that gap.

The AI agent market is fiercely contested by OpenAI, Anthropic, Microsoft, and others, and Google's full-scale entry could accelerate the industry as a whole. Details on Remy's specific features and release timing, however, await an official announcement.

Telus Uses AI to Alter Call Center Operators' Accents

It has been reported that **Telus**, a major Canadian telecom, is using AI to transform call center operators' accents in real time. According to The Globe and Mail, the technology was introduced to enable smoother communication with customers.

The story sparked discussion across multiple Hacker News threads, drawing attention with "19 points and 5 comments." The focus of the debate is the ethics of using AI to alter operators' voices. Critics argue that modifying employees' voices and, by extension, part of their identity in the name of "improving customer satisfaction" reinforces discriminatory messaging against linguistic minorities.

Defenders, on the other hand, contend that reducing language barriers in global call center operations is a reasonable business decision. The commercial use of AI voice transformation raises an important question: where should the line be drawn between worker dignity and efficiency?

FFmpeg Developer Accuses AI Company of OSS License Laundering

A developer of **FFmpeg**, the open source multimedia framework, has accused the AI company OxideAV of misappropriating its license. According to the issue raised on GitHub, OxideAV allegedly incorporated FFmpeg code into its AI products without complying with the original license terms.

The issue exemplifies a growing concern known as "AI license laundering." Incorporating open source code into AI products while evading the original license obligations — such as attribution and source code disclosure — poses a serious threat to the OSS community.

Foundational OSS projects like FFmpeg are embedded in countless commercial products, and if license violations by AI companies become the norm, the sustainability of the entire OSS ecosystem will be undermined. The discussion has also spread on Hacker News, fueling growing interest in how OSS licenses can be enforced in the AI era.

The "Three Cliffs" of Voice AI — UX Breaks Down at 300ms, 500ms, and 800ms

An article published on Qiita has been drawing attention for its practical insights on latency in voice AI. The article reports the results of user testing conducted on a pipeline of STT (speech recognition) → LLM (response generation) → TTS (speech synthesis).

More than half of the testers ended their calls partway through, and an investigation into the cause revealed three distinct latency thresholds:

ms**: The tempo of natural conversation. No discomfort within this range

ms**: The threshold where wait times start to feel noticeable. The rhythm of conversation begins to break down

ms**: UX clearly degrades. Many users mistakenly conclude the call has failed and hang up

These findings show that when developing voice AI, simply "working technically" is not enough — keeping end-to-end latency under 300ms is the lifeline of the user experience. The reports that OpenAI plans to offer low-latency voice AI at scale can be seen as a direct response to precisely this challenge.

---