Disabled Sunshine clients can bypass revocation with a derived client certificate
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
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.
Text from CVE List
Affected versions 2
- Sunshineaffected: >= 2026.329.165800, < 2026.906.222525CVE List
- LizardByte/Sunshine, other>= 2026.329.165800GitHub