CVE-2026-49410

Received Received - Intake

Cross-Site Request Forgery in OpenHuman Desktop App

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-16

Last Modified

2026-10-16

Generated

2026-10-17

AI Q&A

2026-10-17

EPSS Evaluated

N/A

NVD

CVE-2026-49410

Affected Vendors & Products

Vendor	Product	Version / Range
tinyhumansai	openhuman	< 0.56.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-384	Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
CWE-352	The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

Executive Summary

OpenHuman before version 0.56.0 has a cross-site request forgery (CSRF) vulnerability in the unauthenticated GET /auth/telegram loopback callback. The telegram_auth_handler accepts attacker-supplied Telegram login tokens without validating browser fetch metadata or request origin. An attacker can trick a user into visiting a malicious page that triggers a request to the local loopback port 7788, switching the user's active session to the attacker's backend account. This exposes the user's agent actions, memory writes, and Telegram messages to the attacker.

Detection Guidance

Check OpenHuman version with 'openhuman --version' or inspect running processes for versions before 0.56.0. Monitor network traffic on loopback port 7788 for suspicious GET requests to /auth/telegram from external sources.

Impact Analysis

If you use OpenHuman before version 0.56.0, an attacker with an OpenHuman account could hijack your local session by tricking you into visiting a malicious page. This would allow them to access your agent actions, memory writes, and Telegram messages associated with your session. The attacker could then perform actions or extract sensitive data under your identity.

Compliance Impact

This vulnerability could lead to unauthorized access to user data, potentially violating GDPR's data protection principles or HIPAA's requirements for safeguarding protected health information. If exploited, it may result in data breaches, unauthorized processing of personal data, or exposure of sensitive communications, leading to compliance violations and legal consequences.

Mitigation Strategies

Upgrade OpenHuman to version 0.56.0 or later immediately. Disable or restrict access to the /auth/telegram endpoint on loopback port 7788 if not needed. Review active sessions for unauthorized account access.

Hi! I’m here to help you understand CVE-2026-49410. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70