dbcve.org
KeyshotApplication · Luxion

CVE-2025-2530

HIGH · 7.8 CVSS v3.0 Published 2025-03-25
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 DAE 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 dae 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-23698.

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

The vulnerability exists in Luxion KeyShot's DAE (Collada) file parser. During parsing of DAE files, a pointer is accessed without proper initialization, leading to an uninitialized pointer dereference. This allows remote attackers to achieve arbitrary code execution in the context of the current process by tricking users into opening specially crafted malicious DAE files.

MitigationUsers should avoid opening untrusted DAE files from unknown sources. Organizations should implement file type restrictions and sandboxing for file import operations until an official patch is available from Luxion.

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. Confirm Luxion KeyShot is installed
    Check for KeyShot in the program files directory (typically C:\Program Files\Luxion\KeyShot\ or C:\Program Files (x86)\Luxion\KeyShot\) or search for keyshot.exe on the system
    Affected if KeyShot software is present on the system
  2. Identify installed KeyShot version
    Right-click keyshot.exe, select Properties, then view the Details tab for Product Version. Alternatively, open KeyShot and go to Help > About to see the version number
    Affected if The installed version is lower than 2025.1 (e.g., 2024.x, 13.x, etc.)
  3. Verify DAE file import capability is available
    Attempt to import a DAE file through File > Import or by opening a .dae file directly with KeyShot. The vulnerability exists in the DAE parser component
    Affected if DAE file import functionality is accessible and the application can parse DAE files
  4. Confirm the system processes DAE files
    Search for any recently opened or existing DAE files on the system that may have been processed by KeyShot, or check file associations for .dae extension pointing to KeyShot
    Affected if The system has .dae file type associated with KeyShot or users routinely import DAE files

A system is affected if Luxion KeyShot version is installed and is lower than 2025.1, and the DAE file parser feature is accessible to users who could open 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

Users should avoid opening untrusted DAE files from unknown sources. Organizations should implement file type restrictions and sandboxing for file import operations until an official patch is available from Luxion.

Recommended fix High confidence

KeyShot 2025.1

  1. Obtain KeyShot 2025.1 from the official Luxion website (www.keyshot.com)
  2. Back up any existing KeyShot projects, materials, and configurations
  3. Uninstall the current version of KeyShot
  4. Install KeyShot version 2025.1 using the downloaded installer
  5. Launch KeyShot 2025.1 and verify the application runs without errors
  6. Test DAE file parsing functionality to confirm the vulnerability is resolved

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

Fix this in Keyshot Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2530 — 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-2530 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