OpenHuman allows remote inbound channel messages to create unapproved shell cron jobs leading to host command execution
OpenHuman setups with an inbound-capable channel connected can have unapproved shell cron jobs created from remote messages. The fix is in 0.57.13.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.57.13
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.57.13.
- 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? →
- 27/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? →
- Unclear
- 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 sold as a desktop application and Rust library, can be attacked remotely without logging in, by sending messages through a configured external channel. Successful exploitation lets an attacker create persistent shell cron jobs that run with the privileges of the OpenHuman runtime user, leading to command execution on the host and access to data and resources that user can reach.
Read the original description
OpenHuman is an open-source agent harness available as a desktop application and Rust library. Before version 0.57.13, an attacker who can send messages to a configured external channel can cause the agent to create persistent shell cron jobs without human approval. The scheduler later executes these jobs with the privileges of the OpenHuman runtime user. Command validation also permits leading environment assignments that can redirect allowed commands to executable helpers. The demonstrated exploit requires a suitable helper executable already present on the host. This can lead to unauthorized persistent command execution and compromise data and resources accessible to OpenHuman. This issue is fixed in version 0.57.13.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.57.13.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- tinyhumansai openhuman
fixed in 0.57.13
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54143
Is CVE-2026-54143 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?
Remote messages arriving through an inbound-capable channel can create persistent shell cron jobs without approval. Those jobs can run commands on the host as the OpenHuman runtime user, which can reach data that user can access.Source: github.com
Which versions are affected by CVE-2026-54143?
openhuman: before 0.57.13.Source: cve.now feed data
Am I affected, and how do I check?
The affected product is OpenHuman by tinyhumansai, in versions before 0.57.13. The setup involves an inbound-capable channel connected to OpenHuman, and an attacker able to send a message to that channel. To check, compare the installed OpenHuman version with 0.57.13 and review which channels are connected.Source: github.com
How do I fix CVE-2026-54143?
Upgrade OpenHuman to 0.57.13 or later.Source: github.com