Cyber Resilience

CVE-2025-10199

Lizardbyte Sunshine 2025.122.141614

Published
09 September 2025
Modified
03 November 2025
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0018 8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2025-10199 is a high-severity Unquoted Search Path or Element (CWE-428) vulnerability in Lizardbyte Sunshine. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 8th 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.

EU & UK References

Vulnerability Data

A local privilege escalation vulnerability exists in Sunshine for Windows (version v2025.122.141614 and likely prior versions) due to an unquoted service path.

CWE(s)
CWE-428

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-54081Same product: Lizardbyte Sunshine
CVE-2024-31226Same product: Lizardbyte Sunshine
CVE-2025-10198Same product: Lizardbyte Sunshine
CVE-2023-24671Same product: Microsoft Windows
CVE-2024-8996Same product: Microsoft Windows
CVE-2023-22282Same product: Microsoft Windows
CVE-2024-58315Same product: Microsoft Windows
CVE-2024-8975Same product: Microsoft Windows
CVE-2023-29165Same product: Microsoft Windows
CVE-2025-21107Same product: Microsoft Windows

Affected Assets

lizardbyte
sunshine
2025.122.141614

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover unquoted search paths through static analysis or dynamic test cases.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can mandate proper quoting and escaping of path elements.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require safe construction and quoting of search paths and command elements.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent path-handling flaws such as unquoted elements during development.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect unquoted search-path issues before deployment.

A.8.19 Installation of software on operational systems partial match
degrades

Enforcing controlled software installation can prevent unquoted search-path elements in executables and scripts.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices include input validation and path handling that reduce unquoted search-path weaknesses.

A.8.27 Secure system architecture and engineering principles partial match
degrades

Secure system architecture and engineering principles require safe path construction and quoting conventions.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly mandate quoting search paths and avoiding unsafe path construction.

A.8.32 Change management partial match
degrades

Change-management processes can enforce review of path-handling changes that might introduce unquoted elements.

References