<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Telegram-Search - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/telegram-search/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 11 Aug 2026 21:51:09 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/telegram-search/feed.xml" rel="self" type="application/rss+xml"/><item><title>Stored XSS in telegram-search via MessageList.vue</title><link>https://feed.craftedsignal.io/briefs/2026-08-cve-2026-73031/</link><pubDate>Tue, 11 Aug 2026 21:51:09 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-cve-2026-73031/</guid><description>A stored cross-site scripting (XSS) vulnerability (CVE-2026-73031) in telegram-search allows remote attackers to execute arbitrary JavaScript by injecting unsanitized HTML into shared Telegram messages.</description><content:encoded><![CDATA[<p>CVE-2026-73031 identifies a critical stored cross-site scripting (XSS) vulnerability within the telegram-search application. The flaw originates in the MessageList.vue component, specifically within the <code>highlightKeyword</code> function, which processes and renders message content using the Vue.js <code>v-html</code> directive without performing adequate HTML escaping or sanitization. This oversight permits an attacker to inject arbitrary HTML and JavaScript payloads into messages within a shared Telegram group. Because the application processes these messages for searching and viewing, the injected code is stored persistently and executes in the context of any user who views or performs a search operation that includes the malicious message. This is effectively a zero-click execution vector that poses a significant risk for session hijacking or unauthorized actions performed in the victim's browser session.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows remote attackers to execute arbitrary JavaScript in the browsers of legitimate users. This can lead to the exfiltration of session cookies, sensitive user data, or unauthorized actions performed on behalf of the victim. Given the nature of stored XSS in search and message-viewing components, any user interacting with the compromised group or search results is vulnerable, potentially affecting the entire user base of the affected telegram-search deployment.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritize updating the telegram-search application to the latest version that implements proper HTML sanitization for the <code>highlightKeyword</code> function. Audit the codebase to ensure all instances using the <code>v-html</code> directive are coupled with a robust sanitization library like DOMPurify before rendering user-supplied content. Implement a Content Security Policy (CSP) that restricts script execution to trusted sources to mitigate the impact of potential XSS vulnerabilities.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>