Raw vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-1047 is a high-severity Access of Uninitialized Pointer (CWE-824) vulnerability in Luxion Keyshot. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Luxion KeyShot contains an uninitialized pointer vulnerability (CWE-824) in its PVS file parser that permits remote code execution. The flaw occurs when the application accesses a pointer that has not been properly initialized during parsing of specially crafted PVS files, allowing an attacker to execute arbitrary code in the context of the KeyShot process. The issue was reported as ZDI-CAN-23694 and carries a CVSS 3.0 score of 7.8.
An attacker can exploit the vulnerability by convincing a target to open a malicious PVS file or visit a page that delivers such a file. Successful exploitation grants code execution without requiring authentication, although user interaction is mandatory. The attack vector is local with respect to the file system yet can be delivered remotely through standard user workflows.
The EPSS score rose from a low baseline to a peak of 0.0148 on 2026-05-25 before receding to the current value of 0.0038, indicating a measurable increase in exploitation interest after public disclosure. Advisories from Zero Day Initiative and Luxion are available at the referenced URLs, though specific patch or mitigation details are not provided in the source data.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12190
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover uninitialized pointer accesses through static analysis, dynamic testing, or fuzzing before deployment.
Requiring documented development processes and tools enables use of analyzers or coding standards that identify uninitialized pointer defects.
Security engineering principles can mandate memory-safety practices and language choices that structurally avoid uninitialized pointer use.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent uninitialized pointer bugs via coding standards, analysis, and reviews, but eliminating this single weakness only partially fulfills the broader control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uninitialized pointer usage before release.
Secure development life cycle mandates practices that reduce uninitialized pointer defects.
Application security requirements can specify pointer initialization rules.
Secure architecture principles discourage unsafe pointer handling.
Secure coding standards directly prohibit use of uninitialized pointers.