OpenHuman is an open-source agent harness available as a desktop application and Rust library. Versions before 0.56.0 allow cross-site request forgery against the unauthenticated GET /auth/telegram loopback callback because telegram_auth_handler consumes an attacker-supplied one-time Telegram login token and passes the returned JWT to credentials::ops::store_session without validating browser fetch metadata or the request origin. An attacker with an OpenHuman account can cause a user with the local core running to visit a malicious page that requests the /auth/telegram endpoint on loopback port 7788, switching the user's active local session to the attacker's backend account and exposing subsequent agent actions, memory writes, and Telegram messages associated with that session to the attacker. This issue is fixed in version 0.56.0.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → DeferredNVD modified 2026-10-19 21:14
- First seenCVSS 8.1NVD modified 2026-10-16 22:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/tinyhumansai/openhuman/commit/b1bbc53fceed7d1f0cff90cbb0a42f4ab8e153a1
- https://github.com/tinyhumansai/openhuman/pull/2331
- https://github.com/tinyhumansai/openhuman/releases/tag/v0.56.0
- https://github.com/tinyhumansai/openhuman/security/advisories/GHSA-c4m9-hw7m-vv3m
- https://github.com/tinyhumansai/openhuman/security/advisories/GHSA-c4m9-hw7m-vv3m