dbcve.org
SunshineApplication · Lizardbyte

CVE-2026-32253

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-22
Fix available
A fix is available. Upgrade to 2026.516.143833 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Sunshine's custom OpenSSL verify callback in src/crypto.cpp incorrectly treats three error conditions (X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY, X509_V_ERR_CERT_NOT_YET_VALID, and X509_V_ERR_CERT_HAS_EXPIRED) as successful verification. This allows unauthenticated attackers to bypass client-certificate authentication and access protected HTTPS endpoints.

MitigationUpgrade Sunshine to version 2026.516.143833 or later. Until the upgrade is applied, restrict network access to the Sunshine instance to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SunshineApplication
Affected:< 2026.516.143833

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sunshine version
    Run 'sunshine --version' or check the application logs/system information for the Sunshine version number
    Affected if Version is lower than 2026.516.143833 (e.g., 2026.515.x, 2025.x.x, etc.)
  2. Locate Sunshine configuration file
    Find the Sunshine configuration file (typically sunshine.toml in the config directory or application data folder)
    Affected if Configuration file exists and Sunshine is installed
  3. Check for HTTPS endpoint configuration
    Search the configuration file for 'ssl', 'https', 'cert', or 'certificate' settings, or for port configurations using HTTPS (typically port 47989 or similar)
    Affected if HTTPS endpoints are configured in the Sunshine configuration
  4. Verify client certificate authentication settings
    Look for configuration entries related to client certificate verification, such as 'verify_client', 'client_cert', 'ssl_verify_client', or similar TLS/SSL verification parameters
    Affected if Client certificate authentication is explicitly configured or enabled in the settings
  5. Confirm the vulnerable code path is reachable
    Review configuration to determine if HTTPS endpoints with client certificate verification are actively in use for remote connections
    Affected if HTTPS-based remote streaming with certificate authentication is enabled and Sunshine version is below 2026.516.143833

You are affected if Sunshine is running at a version prior to 2026.516.143833 AND client certificate authentication is configured for HTTPS endpoints in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.516.143833 or later
Fixed in 2026.516.143833
Interim mitigation

Upgrade Sunshine to version 2026.516.143833 or later. Until the upgrade is applied, restrict network access to the Sunshine instance to trusted sources only.

Recommended fix High confidence

2026.516.143833

  1. 1. Check current Sunshine version by running `sunshine --version` or checking the application
  2. 2. Download the fixed version 2026.516.143833 from the official Sunshine GitHub releases page
  3. 3. Stop the Sunshine service if running
  4. 4. Install the updated Sunshine package for your platform
  5. 5. Start the Sunshine service
  6. 6. Verify the version has been updated to 2026.516.143833 or later using `sunshine --version`

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sunshine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32253 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32253 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data