telegram-search contains a stored cross-site scripting vulnerability that allows remote attackers to execute arbitrary JavaScript in victims' browsers by sending crafted messages containing unsanitized HTML to a shared Telegram group. The highlightKeyword function in MessageList.vue passes raw message content directly to v-html without HTML escaping or sanitization, enabling stored, cross-user, zero-click execution of injected payloads such as image onerror handlers when victims browse or search messages.
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 1
- First seenCVSS 8.2NVD modified 2026-10-23 20:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://github.com/GramSearch/telegram-search
- https://github.com/GramSearch/telegram-search/issues/653
- https://github.com/GramSearch/telegram-search/pull/654
- https://github.com/groupultra/telegram-search/commit/54f6adced844ce9990228d75e31348bfed934e05
- https://www.vulncheck.com/advisories/telegram-search-stored-xss-via-v-html-in-messagelist-vue