dbcve.org
KeyshotApplication · Luxion

CVE-2025-1047

HIGH · 7.8 CVSS v3.0 Published 2025-04-23
Fix available
A fix is available. Upgrade to 2025.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Luxion KeyShot PVS File Parsing Access of Uninitialized Pointer 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 pvs files. The issue results from the lack of proper initialization of a pointer prior to accessing it. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-23694.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A remote code execution vulnerability exists in Luxion KeyShot's PVS file parser due to an uninitialized pointer being accessed during file parsing. The flaw allows attackers to execute arbitrary code by tricking users into opening malicious .pvs files, leveraging the uninitialized pointer to corrupt memory and redirect execution flow.

MitigationApply vendor patches when available; until then, enforce strict policies against opening untrusted .pvs files and consider application isolation or endpoint detection to mitigate risk.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KeyshotApplication
Affected:< 2025.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed KeyShot version
    Open KeyShot and go to Help > About, or check the executable file properties (right-click KeyShot.exe > Properties > Details) to view the product version
    Affected if The version is lower than 2025.1 (e.g., 2024.x, 13.x, etc.)
  2. Confirm KeyShot handles .pvs files
    Look for .pvs file association in KeyShot (File > Open, or check Windows default programs), or attempt to open a .pvs file with KeyShot to verify the application can parse this format
    Affected if KeyShot is set as the default handler for .pvs files and can open them
  3. Check for recent KeyShot usage
    Review recent documents/files opened in KeyShot, or check Windows recent files for .pvs extensions (search %APPDATA% or recent file lists)
    Affected if Users have opened .pvs files with the vulnerable KeyShot version
  4. Verify KeyShot executable location
    Locate the KeyShot executable (commonly in C:\Program Files\Luxion\KeyShot#\ or C:\Program Files\KeyShot#\) and confirm the version matches the affected range
    Affected if The installed KeyShot executable version is below 2025.1

You are affected if Luxion KeyShot version 2025.1 or later is NOT installed and the application handles .pvs files, allowing potential exploitation via malicious files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.1 or later
Fixed in 2025.1
Interim mitigation

Apply vendor patches when available; until then, enforce strict policies against opening untrusted .pvs files and consider application isolation or endpoint detection to mitigate risk.

Recommended fix High confidence

KeyShot 2025.1

  1. Back up any existing KeyShot projects, materials, and configurations before upgrading
  2. Download KeyShot version 2025.1 from the official source at download.keyshot.com
  3. Run the installer and follow the installation prompts to complete the upgrade
  4. Launch KeyShot and verify the version number shows 2025.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Keyshot Scoped from the published advisory
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1047 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data