Skip to content
Fencer Vulns
high 7.8

CVE-2021-22645 json

Luxion KeyShot versions prior to 10.1, Luxion KeyShot Viewer versions prior to 10.1, Luxion KeyShot Network Rendering versions prior to 10.…

published 2021-02-23 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-9781

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

Luxion KeyShot versions prior to 10.1, Luxion KeyShot Viewer versions prior to 10.1, Luxion KeyShot Network Rendering versions prior to 10.1, and Luxion KeyVR versions prior to 10.1 are vulnerable to an attack because the .bip documents display a “load” command, which can be pointed to a .dll from a remote network share. As a result, the .dll entry point can be executed without sufficient UI warning.

Patch / fix

  • luxion keyshot 10.1
  • luxion keyshot_network_rendering 10.1
  • luxion keyshot_viewer 10.1
  • luxion keyvr 10.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-21-035-01 updated cvss 7.8

Luxion KeyShot (Update A)

  • Luxion KeyShot < 10.1 Luxion KeyShot Network Rendering < 10.1 Luxion KeyShot Viewer < 10.1 Luxion KeyVR < 10.1
    affected: vendor fix keyshot.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • n/a Luxion KeyShot
  • n/a Luxion KeyShot Viewer
  • n/a Luxion KeyShot Network Rendering
  • n/a Luxion KeyVR

Classification

Weakness
  • CWE-357 Insufficient UI Warning of Dangerous Operations

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.