# CVE-2026-73031: telegram-search Stored XSS via v-html in MessageList.vue

> Remote attackers can execute arbitrary JavaScript in victims' browsers via stored XSS in telegram-search by sending crafted messages to shared groups.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-r9w2-wp2g-mfgm

## What is CVE-2026-73031?

CVE-2026-73031 is a high-severity cross-site scripting vulnerability in GramSearch telegram-search, published on 11 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-73031?


## How do I fix CVE-2026-73031?

No fix has been published for CVE-2026-73031 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73031 being exploited?

There is no known exploitation of CVE-2026-73031 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73031 and fix it if it is affected.

What it is: CVE-2026-73031 is a high-severity cross-site scripting vulnerability in GramSearch telegram-search, published on 11 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-73031 in the wild and no public exploit code.

Affected product: GramSearch telegram-search. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73031/ (Markdown: https://insights.sbomify.com/CVE-2026-73031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73031
- OSV: https://osv.dev/vulnerability/CVE-2026-73031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73031/
Summaries are generated and may contain mistakes; the official description above is the record.