# CVE-2026-92202: Luxion KeyShot BIP File Parsing Uncontrolled Search Path Element Remote Code Execution Vulnerability


- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-39qx-cfjv-25gw

## What is CVE-2026-92202?

CVE-2026-92202 is a high-severity vulnerability in Luxion KeyShot, published on 21 Oct 2026. 

### Official description

Luxion KeyShot BIP File Parsing Uncontrolled Search Path Element Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Luxion KeyShot. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of BIP files. The issue results from loading a library from an unsecured location. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-29268.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-92202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92202 is a high-severity vulnerability in Luxion KeyShot, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92202 in the wild and no public exploit code.

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

## Sources

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

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