OpenHuman: Bearer token leaked via approval gate session_id (SQLite plaintext + debug log + RPC response)
Affects OpenHuman before 0.57.5 when a stable bearer token is set via OPENHUMAN_CORE_TOKEN, the documented power-user and remote-core path. Fixed in 0.57.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.57.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Stable bearer token is set via OPENHUMAN_CORE_TOKEN (the documented power-user / remote-core path).
- 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? →
- 14/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, is affected by a flaw in which its approval gate uses the JSON-RPC bearer token as an approval session identifier, causing the token to be stored in plaintext and exposed in logs and RPC responses. A local attacker with low-privilege access can recover the token from these artifacts and use it to access the core RPC interface, potentially exposing sensitive agent and integration data and enabling privileged operations.
Read the original description
OpenHuman is an open-source agent harness available as a desktop application and Rust library. In affected versions before 0.57.5, the approval gate uses the JSON-RPC bearer token as an approval session identifier. This exposes the credential through persisted approval records, events, debug logs, and RPC responses, including during normal desktop operation. An attacker who obtains these artifacts can recover the token and access the core RPC interface while it remains valid. This can expose sensitive agent and integration data and permit privileged operations. Stable tokens remain usable until rotated; launch-specific tokens remain usable while the corresponding core instance is active. The fix is included in version 0.57.5.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Stable bearer token is set via OPENHUMAN_CORE_TOKEN (the documented power-user / remote-core path).Upgrade to a fixed version: 0.57.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tinyhumansai openhuman
fixed in 0.57.5
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-54145
Is CVE-2026-54145 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?
The bearer token that authenticates access to OpenHuman's local JSON-RPC interface can leak through the approval gate session_id. The token is stored in plaintext in SQLite, written to the debug log, and returned in the RPC response. Someone who recovers the token gets full control of the local JSON-RPC surface, including reading agent, integration and config data and invoking any registered method, including writes.Source: github.com
Which versions are affected by CVE-2026-54145?
openhuman: before 0.57.5.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 0.57.5 are affected, and only in setups where a stable bearer token is set through OPENHUMAN_CORE_TOKEN, the documented power-user and remote-core path. To check, look at the installed version and whether OPENHUMAN_CORE_TOKEN is set in the environment that runs the OpenHuman core.Source: github.com
How do I fix CVE-2026-54145?
Upgrade OpenHuman to 0.57.5 or later. The advisory's fixed version is 0.57.5.Source: github.com