Skip to main content
VulnerabilityPublished Updated

CVE-2026-32253: LizardByte Sunshine · Improper Authentication

Affects LizardByte SunshineSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2026.516.143833 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.516.143833
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

What to do

Upgrade Sunshine and lizardbyte/Sunshine to 2026.516.143833.

Affected software

ProductAffectedFixed in
LizardByteSunshineAffected
  • <2026.516.143833
Fixed in
  • 2026.516.143833
GitHublizardbyte/Sunshinepkg:github/lizardbyte/SunshineOther threatsAffected
  • <2026.516.143833
Fixed in
  • 2026.516.143833

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade LizardByte Sunshine to version 2026.516.143833 or later, where this vulnerability has been fixed. Since the vendor advisory confirms the fix in this version, applying this update fully mitigates the issue. No additional mitigations are indicated by the vendor advisory.

Description

Sunshine is a self-hosted game stream host for Moonlight. In versions prior to 2026.516.143833, the client-certificate authentication can be bypassed because of how OpenSSL verification results are handled. In src/crypto.cpp, the custom verify callback treats X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY, X509_V_ERR_CERT_NOT_YET_VALID, and X509_V_ERR_CERT_HAS_EXPIRED as success. This can allow an untrusted certificate to pass authentication and access protected HTTPS endpoints. This issue has been fixed in version 2026.516.143833.

References

Community reviews

Loading reviews…