CVE-2026-111044: high-severity vulnerability in LizardByte Sunshine
Disabled Sunshine clients can bypass revocation with a derived client certificate
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.6epss 0.2%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
Affected products
LizardByte · SunshineRelated CVEs — LizardByte Sunshine
In the same product, most dangerous first.
CVE-2024-51738HIGHSunshine improperly enforces pairing protocol request orderEPSS 0.6%CVE-2024-31221MEDIUMClients removed during unpairing process may regain access if Sunshine was not restartedEPSS 0.5%CVE-2024-31220HIGHSunshine vulnerable to remote unauthenticated arbitrary file readEPSS 0.5%CVE-2024-45407MEDIUMSunshine has incorrect state management during pairing process may lead to incorrectly authorized clientEPSS 0.3%CVE-2026-32253CRITICALSunshine: Authentication bypass via improper client certificate validationEPSS 0.3%CVE-2025-53096MEDIUMSunshine clickjacking in the UI leads to unauthorized actions being performedEPSS 0.2%