OpenHuman: Bearer token leak via process environment variable on macOS (same-UID local RCE primitive)
Affects OpenHuman 0.53.15 up to but not including 0.57.5 on macOS (Intel and Apple Silicon); other processes running as the same user can read the bearer token. Fixed in 0.57.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.57.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions are OpenHuman 0.53.15 up to but not including 0.57.5 (the advisory lists affected as >= 0.53.15, < 0.57.5). Target is the macOS desktop build of OpenHuman (Intel and Apple Silicon). The attacker process must run as the same user (same UID) as the OpenHuman desktop app.
- 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? →
- 14/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? →
- Specific setups only
- 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's macOS desktop application exposes its per-launch core bearer token in a process environment variable, so a local attacker with low-privilege access can recover it and authenticate to the core JSON-RPC service. From there, the attacker can read agent memory and integrated-account data, invoke privileged actions, change configuration, and stop or disrupt services, all without root access.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions are OpenHuman 0.53.15 up to but not including 0.57.5 (the advisory lists affected as >= 0.53.15, < 0.57.5). Target is the macOS desktop build of OpenHuman (Intel and Apple Silicon). The attacker process must run as the same user (same UID) as the OpenHuman desktop app.Upgrade to a fixed version: 0.57.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tinyhumansai openhuman
From 0.53.15 · fixed in 0.57.5
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54146
Is CVE-2026-54146 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?
OpenHuman's bearer token can be read from the process environment on macOS. Any other process running under the same user account can read it without elevated privileges.Source: github.com
Which versions are affected by CVE-2026-54146?
openhuman: from 0.53.15 before 0.57.5.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 0.53.15 up to but not including 0.57.5 of the macOS desktop build, on both Intel (x86_64) and Apple Silicon (aarch64). Compare the installed OpenHuman version against that range to check the version side.Source: github.com
How do I fix CVE-2026-54146?
Upgrade to OpenHuman 0.57.5 or later, the first version listed as fixed.Source: github.com