CVE-2026-73031 GramSearch CVE debrief

Who should care

Defenders responsible for telegram-search deployments, especially those exposed to untrusted input, should assess and mitigate this vulnerability. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-73031 is a stored cross-site scripting vulnerability in telegram-search that allows remote attackers to execute arbitrary JavaScript in victims' browsers.

• Remote attackers can execute arbitrary JavaScript in victims' browsers
• Victims' browsers can be compromised by crafted messages containing unsanitized HTML
• Defenders must verify and apply patches or mitigations
• telegram-search deployments are at risk of exploitation

Technical summary

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. This vulnerability allows remote attackers to execute arbitrary JavaScript in victims' browsers by sending crafted messages containing unsanitized HTML to a shared Telegram group. Defenders should prioritize verifying and mitigating this vulnerability in telegram-search deployments, especially those exposed to untrusted input.

Defensive priority

Defenders should prioritize verifying and mitigating this vulnerability in telegram-search deployments, especially those exposed to untrusted input.

Recommended defensive actions

• Verify and apply the patch referenced in the source references
• Implement HTML escaping or sanitization for message content in MessageList.vue
• Restrict input to trusted sources
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is caused by the highlightKeyword function in MessageList.vue passing raw message content directly to v-html without HTML escaping or sanitization. This allows stored, cross-user, zero-click execution of injected payloads such as image onerror handlers when victims browse or search messages. Defenders should verify and apply patches or mitigations, and monitor for suspicious activity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.