CVE-2026-49405 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
OpenHuman's local server exposes an event stream at /events without authentication and allows cross-origin browser access. A local client or a malicious web page the victim opens can subscribe to another client's stream and read assistant responses, tool arguments and raw tool outputs.
first public Oct 9, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Anyone running the OpenHuman desktop application or Rust library before 0.56.0 with its local server active. The exposure is through the local server's event endpoint, so a team running OpenHuman on shared machines or as a library in a service should look first; installs that do not run the local server are less exposed.
Not affected if local-server-disabled, version-0.56.0-or-later
Who cares ai-agents, desktop, openhuman, rust
0.56.0./events.0.56.0 or later.OpenHuman is an open-source agent harness available as a desktop application and Rust library. Before 0.56.0, the local server exposes the server-sent events endpoint at /events without bearer authentication, permits cross-origin browser access, and uses only a caller-supplied client_id to select WebChannelEvent objects from the process-wide event bus. An unauthenticated local client, or an attacker-hosted web page opened by the victim, can subscribe to another client's stream by supplying a known or guessed identifier; the fixed system identifier makes the proactive-message stream predictable. The exposed events can include complete assistant responses, streamed message content, tool names, tool arguments, and raw tool outputs intended for the local user interface. This issue is fixed in version 0.56.0.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.