CVE-2026-54145 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
OpenHuman is an open-source agent harness for desktop and Rust. Before version 0.57.5 its approval gate reuses the JSON-RPC bearer token as an approval session identifier, so the token is written into approval records, events, debug logs and RPC responses.
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 OpenHuman before version 0.57.5 on a desktop, since the approval flow exposes the RPC token during normal operation. An attacker who reads the persisted logs or records can use the token while it remains valid, and stable tokens stay valid until rotated. Systems on a current version are not affected.
Not affected if version-0.57.5-or-later
Who cares agent-harness, desktop, openhuman, rust
0.57.50.57.5 or laterOpenHuman 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.
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.