CVE-2026-110768 in holaOSinfo

Summary

by MITRE • 10/15/2026

holaOS through 2026.822.1 contains an authorization bypass vulnerability in the channel-gateway Telegram connector that authorizes senders by mutable username rather than only numeric id. Attackers who register a released username listed in allowFrom can submit turns to the bound workspace agent, which runs configured tools on the operator's machine.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 10/15/2026

The identified security flaw resides within holaOS versions up through 2026.822.1, specifically affecting the channel-gateway Telegram connector component. This vulnerability constitutes a critical authorization bypass that stems from an improper implementation of identity verification mechanisms. The core technical deficiency lies in how the system authenticates incoming requests by relying on mutable username identifiers rather than immutable numeric user IDs. In many messaging platforms, including Telegram, usernames are human-readable strings that can be changed or reassigned over time. By trusting these volatile attributes for authorization decisions, the application fails to maintain a consistent and reliable mapping between the logical identity of the sender and their actual account instance. This design choice introduces a significant attack surface where an adversary can manipulate their perceived identity within the context of the authorized senders list.

The operational impact of this vulnerability is severe due to the privileged nature of the target system. The bound workspace agent, which receives these unauthorized requests, possesses the capability to execute configured tools directly on the operator's machine. This effectively grants remote code execution capabilities under the guise of a legitimate user when an attacker exploits the username reassignment logic. An adversary can register for a previously released or available username that is currently listed in the allowFrom configuration parameter. By doing so, they trick the channel-gateway into treating their requests as if they originate from an authorized entity. Once authenticated via this flawed mechanism, the attacker can submit turns to the workspace agent, triggering the execution of arbitrary tools and commands on the victim's system without proper authorization checks.

This vulnerability aligns with Common Weakness Enumeration (CWE) category CWE-287, which describes Improper Authentication, as well as CWE-640, Weak Password Recovery Mechanism for Administrators if applicable to account recovery flows, though primarily it is an identity management failure often categorized under CWE-359 Exposure of Unique Identifier. From a tactical perspective, this exploitation path corresponds to MITRE ATT&CK technique T1078 Valid Accounts, where attackers use legitimate credentials or identities to bypass security controls. The ability to execute tools on the operator's machine further escalates the risk to techniques such as T1059 Command and Scripting Interpreter if shell commands are executed, or T1203 Executable File Execution depending on the specific tool invoked by the workspace agent.

Mitigation strategies must focus on enforcing strict identity verification using immutable identifiers. The channel-gateway connector should be updated to validate incoming requests exclusively against numeric user IDs rather than mutable usernames. This ensures that even if an attacker changes their username or registers a new one, they cannot impersonate another authorized user whose ID remains distinct and unchangeable. Additionally, implementing input validation on the allowFrom list to ensure it references stable identifiers is crucial. Regular security audits of authentication logic in messaging integrations are recommended to prevent similar identity spoofing vulnerabilities. Patching holaOS to a version that resolves this authorization bypass is essential for maintaining system integrity and preventing unauthorized remote execution capabilities.

Responsible

VulnCheck

Reservation

10/14/2026

Disclosure

10/15/2026

Moderation

accepted

EPSS

0.00220

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!