dbcve.org
KeyshotApplication · Luxion

CVE-2025-2531

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 Heap-based Buffer Overflow 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 validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-23704.

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

Heap-based buffer overflow in Luxion KeyShot's DAE (Collada) file parser. The vulnerability stems from insufficient validation of user-supplied data length before copying into a heap-allocated buffer, allowing remote code execution when a user opens a specially crafted malicious DAE file.

MitigationApply vendor patch from Luxion when available; until then, avoid opening untrusted DAE files and restrict KeyShot usage to trusted file sources.

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. Locate KeyShot installation directory
    Search for KeyShot installation folders, typically in Program Files or Program Files (x86) on Windows, or /Applications on macOS. Check for folders named 'KeyShot' or 'Luxion KeyShot'.
    Affected if KeyShot is installed on the system
  2. Identify installed KeyShot version
    Open KeyShot and navigate to Help > About, or check the version in the installer executable name. On Windows, you may also check the file properties of the KeyShot.exe binary.
    Affected if Installed version is lower than 2025.1
  3. Verify DAE file handling capability
    Check if KeyShot can import DAE (Collada) files by attempting to open a DAE file or checking file association settings. DAE import is a built-in feature in KeyShot.
    Affected if DAE file import functionality is available and enabled in KeyShot
  4. Review recent DAE file access
    Check browser download history, Windows Recent Items, or file explorer recent files for any DAE files opened with KeyShot. On Windows, search for .dae files in recent documents or the Downloads folder.
    Affected if User has recently opened DAE files from untrusted sources using KeyShot

You are affected if KeyShot version is installed and is lower than 2025.1, and DAE files can be opened or have been opened with the software.

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 patch from Luxion when available; until then, avoid opening untrusted DAE files and restrict KeyShot usage to trusted file sources.

Recommended fix High confidence

2025.1

  1. 1. Close any running instances of KeyShot
  2. 2. Back up your current KeyShot projects and settings
  3. 3. Download KeyShot version 2025.1 from the official Luxion website or your licensed download location
  4. 4. Run the installer for KeyShot 2025.1
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. After installation, verify the version by checking Help > About KeyShot to confirm version 2025.1 is installed
  7. 7. Test that DAE files load correctly in the updated version
Caveat Review release notes for version 2025.1 to check for any workflow changes or deprecated features that may affect existing workflows

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

Fix this in Keyshot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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