# CVE-2026-9046: Privilege escalation in App Store

> Local attackers can execute arbitrary code if Lenovo Legion Zone or App Store are installed on a non-system partition due to insecure permissions.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-6j6v-724c-h5fm

## What is CVE-2026-9046?

CVE-2026-9046 is a high-severity vulnerability in Lenovo App Store, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential insecure permissions vulnerability was reported in Legion Zone and the Lenovo App Store Windows applications, distributed exclusively in the Chinese market, that when installed on a non‑system partition, could allow a local user to execute arbitrary code.

Weakness: CWE-277 (Insecure Inherited Permissions)

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


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

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

## Is CVE-2026-9046 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9046 is a high-severity vulnerability in Lenovo App Store, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9046 in the wild and no public exploit code.

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

## Sources

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

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