Skip to content
Fencer Intel
high 7.8

CVE-2021-22643 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 5y ago modified 4mo ago also EUVD-2021-9779

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
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 out-of-bounds read while processing project files, which may allow an attacker to execute arbitrary code.

Patch / fix

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

Is CVE-2021-22643 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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

2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

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

References

Sources

Fencer Intel 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.