# CVE-2025-54081: SunshineService Has Unquoted Service Path That Allows Local SYSTEM Code Execution

> Local attackers can execute arbitrary code with SYSTEM privileges if Sunshine is installed in a directory with spaces due to an unquoted service path.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 23 Sep 2025
- **Also known as:** GHSA-6p7j-5v8v-w45h

## What is CVE-2025-54081?

CVE-2025-54081 is a medium-severity vulnerability in LizardByte Sunshine, published on 23 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Sunshine is a self-hosted game stream host for Moonlight. Prior to version 2025.923.33222, the Windows service SunshineService is installed with an unquoted executable path. If Sunshine is installed in a directory whose name includes a space, the Service Control Manager (SCM) interprets the path incrementally and may execute a malicious binary placed earlier in the search string. This issue has been patched in version 2025.923.33222.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2025-54081?

It affects 1 product.


Products: Lizardbyte Sunshine.

## How do I fix CVE-2025-54081?

No fix has been published for CVE-2025-54081 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-54081 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54081 exists.

## Other vulnerabilities in LizardByte Sunshine

- [CVE-2026-32253](https://insights.sbomify.com/CVE-2026-32253/): Sunshine: Authentication bypass via improper client certificate validation (critical 9.8)
- [CVE-2025-53095](https://insights.sbomify.com/CVE-2025-53095/): Sunshine application-wide CSRF in the UI leads to command injection as Administrator (critical 9.7)
- [CVE-2025-10198](https://insights.sbomify.com/CVE-2025-10198/): LizardBytes Sunshine for Windows contains a DLL search-order hijacking vulnerability (high 7.8)
- [CVE-2025-10199](https://insights.sbomify.com/CVE-2025-10199/): A local privilege escalation vulnerability exists in LizardBytes' Sunshine for Windows (high 7.8)
- [CVE-2024-51738](https://insights.sbomify.com/CVE-2024-51738/): Sunshine improperly enforces pairing protocol request order (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54081 and fix it if it is affected.

What it is: CVE-2025-54081 is a medium-severity vulnerability in LizardByte Sunshine, published on 23 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54081 exists.

Affected product: LizardByte Sunshine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54081/ (Markdown: https://insights.sbomify.com/CVE-2025-54081/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54081
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54081
- OSV: https://osv.dev/vulnerability/CVE-2025-54081

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54081/
Summaries are generated and may contain mistakes; the official description above is the record.