# CVE-2026-6090: Auth bypass in Smart Connect

> A local authenticated user can bypass authentication in Lenovo Smart Connect to execute arbitrary code with elevated privileges.

- **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:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-q34g-8v67-vv99

## What is CVE-2026-6090?

CVE-2026-6090 is a high-severity authentication bypass vulnerability in Lenovo Smart Connect, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential authentication bypass was reported in Lenovo Smart Connect for Windows that could allow a local authenticated user to execute arbitrary code with elevated privileges.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-6090 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6090 is a high-severity authentication bypass vulnerability in Lenovo Smart Connect, published on 10 Jun 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-6090 in the wild and no public exploit code.

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

## Sources

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

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