# CVE-2026-12036: Path traversal in Vantage

> A local authenticated user can delete arbitrary files with elevated privileges in Lenovo Vantage due to improper link following.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-f95j-cwmr-fqw7

## What is CVE-2026-12036?

CVE-2026-12036 is a medium-severity path traversal vulnerability in Lenovo Vantage, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper link following vulnerability was reported in the VantageCoreAddin for Lenovo Vantage and Lenovo Commercial Vantage that could allow a local authenticated user to perform an arbitrary file deletion with elevated privileges.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-12036 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12036 is a medium-severity path traversal vulnerability in Lenovo Vantage, published on 13 Aug 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-12036 in the wild and no public exploit code.

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

## Sources

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

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