# CVE-2026-7516: Other in Application

> A vulnerability in Lenovo's Android tablet application allows malicious websites to overwrite system clipboard contents via the built-in browser.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-wx95-xvqf-3525

## What is CVE-2026-7516?

CVE-2026-7516 is a medium-severity vulnerability in Lenovo Application, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was identified in the Lenovo Android Application, distributed exclusively on tablets in the Chinese market, that could allow a website visited by the built-in browser to overwrite system clipboard contents.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

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

## Is CVE-2026-7516 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7516 is a medium-severity vulnerability in Lenovo Application, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-7516 in the wild and no public exploit code.

Affected product: Lenovo Application. 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-7516/ (Markdown: https://insights.sbomify.com/CVE-2026-7516/index.md)
```

## Sources

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

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