holaOS through 2026.822.1 Authorization Bypass via Telegram Connector Username Allowlist

Code

The project this record applies to. Exploit listings stay in References.

• Repository · github.com

Timeline

Detection, updates, and resolution for this record.

1. Oct 14, 2026 · NIST NVD

   Detected

   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.

2. Oct 15, 2026 · NIST NVD

   Updated

   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.

Affected

• vendor holaboss-ai holaOSversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-110768

  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

  cve.org
• FIRST EPSSExploitation probabilityCVE-2026-110768

  30-day exploitation probability 0.2%

  first.org
• NIST NVDVulnerability recordCVE-2026-110768

  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

  nvd.nist.gov

References

• Reference · github.com
• Reference · github.com
• Reference · hackmd.io
• Reference · vulncheck.com