# CVE-2026-4145: Privilege escalation in Software Fix

> A local authenticated user can execute arbitrary code with elevated privileges in Lenovo Software Fix, requiring a patch to mitigate.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/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:** 15 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-p4rv-88gx-v3fc

## What is CVE-2026-4145?

CVE-2026-4145 is a high-severity vulnerability in Lenovo Software Fix, published on 15 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

During an internal security assessment, a potential vulnerability was discovered in Lenovo Software Fix that could allow a local authenticated user to perform arbitrary code execution with elevated privileges.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Lenovo Software Fix.

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

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

## Is CVE-2026-4145 being exploited?

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

## Other vulnerabilities in Lenovo Software Fix

- [CVE-2026-4134](https://insights.sbomify.com/CVE-2026-4134/): Privilege escalation in Software Fix (high 7.0)
- [CVE-2026-4135](https://insights.sbomify.com/CVE-2026-4135/): Path traversal in Software Fix (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4145 is a high-severity vulnerability in Lenovo Software Fix, published on 15 Apr 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-4145 in the wild and no public exploit code.

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

## Sources

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

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