OpenHuman: Unauthenticated server-sent events endpoint leaks user-facing event data
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 0.56.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.56.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
OpenHuman, an open-source agent harness available as a desktop app and Rust library, exposes an event stream endpoint without authentication, so a local attacker can read another client's assistant responses, message content, tool names, tool arguments, and raw tool outputs without logging in or taking any user action. The attacker only needs to know or guess the client identifier, which is fixed and predictable for the system stream.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.2/10CVSS 6.2
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.56.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- tinyhumansai openhuman
fixed in 0.56.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-49405
Is CVE-2026-49405 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-49405?
openhuman: before 0.56.0.Source: cve.now feed data
How do I fix CVE-2026-49405?
Upgrade to a fixed version: 0.56.0.Source: cve.now feed data