CVE-2026-73031
Stored XSS in telegram-search allows remote JavaScript execution when viewing/searching messages.
Is CVE-2026-73031 being exploited?
Not confirmed. CVE-2026-73031 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-73031?
CVE-2026-73031 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73031?
Not known from our data. No patch reference has been recorded for CVE-2026-73031, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-73031 affect?
CVE-2026-73031 affects telegram-search (web client), MessageList.vue component, Telegram group message search feature. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73031?
Sanitize/escape message HTML, remove v-html usage, apply vendor patch or disable HTML rendering.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored cross-site scripting via unsanitized v-html enables remote JS execution, theft of cookies/tokens, account takeover and actions as the victim.
Immediate action required
- affected<= 1.2.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.