CVE-2026-54141 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
OpenHuman is an open-source agent harness; before 0.57.13, a direct message from an outside sender on a configured Yuanbao channel could make the agent run JavaScript and operating-system commands. The approval gate skipped its prompt for these messages, so the commands ran as the OpenHuman user.
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.
Teams running OpenHuman as an agent harness with a Yuanbao channel configured and Node enabled under the default Supervised policy. Direct messages on Yuanbao are open by default, so any sender who can message the bot can reach the flaw. Installations without a Yuanbao channel or with Node disabled are not exposed by this path.
Not affected if no-yuanbao-channel, node-disabled, version-0.57.13-or-later
Who cares agent-harness, desktop, node, openhuman, yuanbao
0.57.130.57.13 or laterOpenHuman is an open-source agent harness available as a desktop application and Rust library. Before 0.57.13, a remote direct message received through a configured Yuanbao channel is converted into a generic channel AgentTurnRequest that uses the default tool policy without establishing an interactive approval context. Under the default Supervised autonomy policy with Node enabled, node_exec is classified as a write operation that should prompt for approval, but ApprovalGate treats missing APPROVAL_CHAT_CONTEXT as a non-interactive turn and allows execution. Because Yuanbao direct messages are open by default, an external sender who can message the connected bot can influence the agent to execute JavaScript and operating-system commands as the OpenHuman user without an approval prompt. The issue requires a configured Yuanbao channel, the default approval-requiring policy state, Node availability, and successful model selection of node_exec. This issue is fixed in version 0.57.13.
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.