CVE-2026-54144 · Other
NO FIX YET · SEE WHAT TO DO
OpenHuman's embedded browser shim let page JavaScript call getDisplayMedia without a user click, and the embedded Chromium then auto-selected the primary display. An attacker who runs JavaScript in an allowed embedded origin, such as Google Meet, can get a live desktop capture stream showing chats, documents, code, email and one-time codes.
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.
Only macOS installs of OpenHuman before 0.56.0 that have Screen Recording permission granted are exposed. The attack needs script execution inside one of the app's allowed embedded web origins, such as Google Meet. Installs without Screen Recording permission, non-macOS installs, and the Rust library used without the desktop app are not described as affected.
Not affected if no-screen-recording-permission, non-macos, version-0.56.0-or-later
Who cares agent-harness, desktop, macos, openhuman
0.56.0.0.56.0 or later.OpenHuman is an open-source agent harness available as a desktop application and Rust library. Before 0.56.0 on macOS, the runtime injected into a supported remote account webview such as Google Meet allows page JavaScript to call getDisplayMedia without a live user gesture. Instead of rejecting the request, the shim falls through to native Chromium capture behavior, and the embedded CEF environment can auto-select the primary display because it lacks the normal desktop-media picker. If OpenHuman already has macOS Screen Recording permission and an attacker obtains JavaScript execution in an allowed embedded origin, the attacker can obtain a real desktop capture stream without a new user gesture. The stream can expose chats, documents, source code, email, meeting content, credentials, one-time codes, and other visible desktop information. The separate direct screen_share_begin_session IPC path failing origin validation does not prevent exploitation through getDisplayMedia. This issue is fixed in version 0.56.0.
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.