Find notable cyber news and cases, enriched with sources, timelines, and signals.
Home Watchlists Beta Browse News Feed Stats About Contact

NVIDIA NemoClaw Ollama browser-to-localhost control security flaw

Vulnerability
First reported
Last updated
Happening score
H score 15
1 unique sources, 1 articles

Summary

Hide ▲

A malicious webpage can exploit NVIDIA NemoClaw's Ollama backend when it is bound to 0.0.0.0:11434, enabling unauthenticated local control of the model API. The attacker can use DNS rebinding to reach the local service and overwrite the model's chat template. That can plant hidden instructions that persist across later conversations.

Related Happenings

CDP-Enable-BOF activates Chrome DevTools Protocol inside live Windows browsers for post-exploitation session access

Technical Analysis
H score23 First: 14.08.2026 14:07 Last: 14.08.2026 14:07 Sources 1

About this happening: CDP-Enable-BOF now enables Chrome DevTools Protocol access inside a live Google Chrome or Microsoft Edge process on Windows, raising the risk of cookie theft...

Open Happening

LabubaRAT Rust RAT masquerading as NVIDIA software on Windows

Malware Activity
H score24 First: 14.07.2026 19:52 Last: 14.07.2026 19:52 Sources 1

About this happening: A newly documented Rust-based RAT, LabubaRAT, now gives operators Windows host control with file movement, screenshot capture, and traffic proxying. The malware masq...

Open Happening

OpenClaw ClawJacked localhost WebSocket brute-force security flaw

Vulnerability
H score37 First: 01.03.2026 23:44 Last: 01.03.2026 23:44 Sources 1

About this happening: OpenClaw’s ClawJacked vulnerability allowed a malicious website to brute-force a localhost WebSocket connection and take control of a local instance, putting ses...

Open Happening

Timeline

  1. 25.08.2026 17:07 1 articles · 2h ago

    Oasis Security discloses NemoClaw browser-to-localhost flaw

    Initial Disclosure

    Oasis Security disclosed a weakness in NVIDIA NemoClaw that lets an attacker-controlled webpage use DNS rebinding to reach the local Ollama API on port 11434, take unauthenticated control of the model server, and plant hidden instructions that persist across later conversations. Oasis Security also reported the issue to NVIDIA's PSIRT, and no exploitation had been reported as of August 25, 2026.

    Show sources
    Open in new tab
  2. 25.08.2026 17:07 2 articles · 2h ago

    NemoClaw proxy blocks non-loopback Ollama backends

    Technical Analysis Update

    A review of the NemoClaw repository on August 25, 2026 found that the local Ollama proxy refuses to start against a backend that is not bound to loopback, with a documented override via NEMOCLAW_OLLAMA_PROXY_SKIP_BIND_PROBE=1. The same code path ties local operation to OLLAMA_HOST=127.0.0.1:${port}, reinforcing loopback-only access for the Ollama daemon.

    Show sources
    Open in new tab