---
id: "CVE-2026-54145"
kind: "vulnerability"
aliases: ["CVE-2026-54145"]
title: "OpenHuman agent harness leaks its RPC bearer token through approval records"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["agent-harness", "ai-tooling", "desktop", "openhuman", "rust"]
not_affected_if: ["version-0.57.5-or-later"]
published_at: "2026-11-05T17:18:19+00:00"
first_seen_at: "2026-11-05T17:40:04+00:00"
updated_at: "2026-11-05T17:42:08+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54145", "first_seen_at": "2026-11-05T17:40:04+00:00"}]
exploit_sources: []
---

# OpenHuman agent harness leaks its RPC bearer token through approval records

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed OpenHuman version against the fixed release `0.57.5`
- Look for the token in persisted approval records and debug logs on the desktop machine (locations not stated in sources: unknown)

## Fix

- OpenHuman: move to version `0.57.5` or later

## Timeline

- 2026-11-05T17:40:04+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-54145

## Documents

- [advisory] Vendor advisory: github.com https://github.com/tinyhumansai/openhuman/security/advisories/GHSA-ww8p-c82p-p8wx
- [fix] Patch: github.com https://github.com/tinyhumansai/openhuman/commit/c5ff4a3516a9ad889b19a97eb1bba624908658fe
- [fix] Release notes: github.com https://github.com/tinyhumansai/openhuman/releases/tag/v0.57.5

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_