LizardByte Sunshine
Disabled Sunshine clients can bypass revocation with a derived client certificate
Sunshine is a self-hosted game stream host for Moonlight. From 2026.329.165800 until 2026.906.222525, Sunshine accepted any client certificate that chained to a stored paired-client certificate, but it did not require the presented certificate to be the exact enabled paired identity. Certificate text was also compared without canonicalizing equivalent PEM encodings. A previously paired client that retains its private key can present an alternate certificate derived from its paired certificate and bypass the Disable control. Equivalent PEM encodings could also cause inconsistent client identity handling. A client that was never paired cannot use this issue, and removing the paired client removes its trust relationship. This issue is fixed in version 2026.906.222525.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2026.329.165800, < 2026.906.222525
Fixed in 2026.906.222525
Mitigation
Upgrade Sunshine to 2026.906.222525 or later.
References
- Vendor advisory github.com/LizardByte/Sunshine/security/adviso…
- Patch github.com/LizardByte/Sunshine/commit/4d768847…
- Release notes github.com/LizardByte/Sunshine/releases/tag/v2…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.