OpenHuman: Unauthenticated Socket.IO RPC bypass allows invoking protected OpenHuman core controllers without the Bearer token
Affects OpenHuman versions before 0.56.0 when the Socket.IO listener is enabled. The fix is in 0.56.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.56.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The Socket.IO listener is enabled.
- 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? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- 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
Summary
OpenHuman, an open-source agent harness available as a desktop application and Rust library, has a flaw before version 0.56.0 in which its Socket.IO handlers skip the bearer-token check that protects HTTP requests to /rpc. A local attacker with no login can use that path to call protected controllers, which can read configuration or health data, start agent flows, alter local data, or stop and restart services, depending on the method chosen.
Read the original description
OpenHuman is an open-source agent harness available as a desktop application and Rust library. Before 0.56.0, the core server protects HTTP POST requests to /rpc with bearer middleware but exposes Socket.IO rpc:request and chat:start handlers without equivalent transport or handler-level authentication. A local unauthenticated client can connect to the Socket.IO namespace and dispatch requests through the same protected controller path that rejects a missing bearer on /rpc. Depending on the selected method, the attacker can read configuration or health data, start agent flows, interact with integrated account APIs, alter local data, or stop and restart services. This issue is fixed in version 0.56.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The Socket.IO listener is enabled.Upgrade to a fixed version: 0.56.0.
Timeline
- CVE published
- First seen by cve.now
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-49393
Is CVE-2026-49393 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in OpenHuman's Socket.IO RPC handling lets an unauthenticated client invoke protected core controllers without the Bearer token that should be required.Source: github.com
Which versions are affected by CVE-2026-49393?
openhuman: before 0.56.0.Source: cve.now feed data
Am I affected, and how do I check?
The advisory applies to OpenHuman builds before 0.56.0 where the Socket.IO listener is enabled, per the quoted condition that the bypass applies when Socket.IO is enabled. To check, confirm the installed OpenHuman version and whether the Socket.IO listener is turned on in its configuration.Source: github.com
How do I fix CVE-2026-49393?
Upgrade OpenHuman to version 0.56.0 or later, which contains the fix.Source: github.com