CVE-2026-54146 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
OpenHuman's macOS desktop app places its per-launch core bearer token in the process environment, where another process running as the same user can read it. The attacker can then authenticate to the local core JSON-RPC service and read agent memory and connected-account data, invoke privileged actions, and change configuration.
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.
Affects macOS installs of the OpenHuman desktop application and Rust library from 0.53.15 before 0.57.5, on Intel and Apple Silicon. Exposure requires another local process running as the same user, so it is a local-only risk on shared or multi-user-session machines and mostly a concern for developer workstations running the agent.
Not affected if non-macos, version-0.57.5-or-later
Who cares agent-harness, desktop, macos, openhuman, rust
0.53.15 before 0.57.5.0.57.5.OpenHuman is an open-source agent harness available as a desktop application and Rust library. From 0.53.15 before 0.57.5 on macOS, core_process.rs in the Tauri desktop process publishes the per-launch OPENHUMAN_CORE_TOKEN bearer credential in its process environment even though the core now runs as an in-process task. Another process running as the same user can read that environment through the macOS KERN_PROCARGS2 process-inspection interface, recover the token together with the local host and port, and authenticate to the core JSON-RPC service with the authority of the desktop frontend. The attacker can read agent memory and integrated-account data, invoke privileged actions, change configuration, and stop or disrupt services without root access, developer mode, or changes to System Integrity Protection. This issue affects Intel and Apple Silicon macOS systems. This issue is fixed 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.