CVE-2026-110768

Deferred Deferred - Pending Action

Authorization Bypass in holaOS Telegram Connector via Mutable Username

Publication date: 2026-10-14

Last updated on: 2026-10-14

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-14

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-110768

EUVD

EUVD-2026-101568

Affected Vendors & Products

Vendor	Product	Version / Range
holaboss-ai	holaOS	0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-290	This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

Executive Summary

holaOS versions up to 2026.822.1 contain an authorization bypass in the Telegram connector of the channel-gateway component. The system authorizes senders based on mutable usernames instead of immutable numeric IDs. Attackers can register a username listed in the allowlist (allowFrom) and submit commands to the workspace agent, which executes configured tools on the operator's machine.

Detection Guidance

Check holaOS logs for unauthorized Telegram bot interactions or unexpected tool executions. Inspect the channel-gateway configuration for empty allowlists or mutable username-based authorization. Review Telegram bot API traffic for messages from unrecognized usernames listed in allowFrom.

Impact Analysis

An attacker could exploit this to send arbitrary tasks to your holaOS workspace agent. The agent may execute tools with local shell, filesystem, browser, or coding-agent access, potentially leading to unauthorized actions on your machine. Default configurations with empty allowlists allow any Telegram user to interact with the bot.

The agent runs with full tool set permissions, including runtime and MCP tools, enabling significant control over the system if compromised.

Compliance Impact

This vulnerability could lead to unauthorized access and execution of tools on the operator's machine, potentially violating data protection requirements under GDPR or HIPAA. Unauthorized tool execution may result in data exfiltration, unauthorized modifications, or breaches of confidentiality if sensitive data is processed or exposed.

Mitigation Strategies

Update holaOS to the latest version (2026.822.1 or later). Configure the Telegram connector to use immutable numeric IDs instead of usernames. Ensure the allowlist is populated with only trusted senders and never left empty.

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

0/70