CVE-2026-111044 LizardByte CVE debrief

Who should care

Defenders responsible for managing and maintaining Sunshine installations should be aware of this vulnerability and take steps to verify and update their installations. They should review and update client certificates to ensure proper validation and monitor for potential exploitation attempts. Security teams and operators of affected platforms should prioritize verifying their Sunshine installation and ensuring it is updated to the latest version.

Why it matters

A vulnerability in Sunshine allows clients to bypass the Disable control, potentially leading to unauthorized access. Defenders should prioritize verifying their Sunshine installation and ensuring it is updated to the latest version.

• Verify and update Sunshine installations to prevent potential exploitation
• Review and update client certificates to ensure proper validation
• Monitor for potential exploitation attempts

Technical summary

The vulnerability in Sunshine allowed clients to bypass the Disable control by presenting an alternate certificate derived from a paired client certificate. This was due to improper validation of client certificates, which did not require the presented certificate to be the exact enabled paired identity. The issue was fixed in version 2026.906.222525. 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.

Defensive priority

Defenders should prioritize verifying their Sunshine installation and ensuring it is updated to the latest version.

Recommended defensive actions

• Verify Sunshine installation and update to the latest version
• Review and update client certificates to ensure proper validation
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, its impact, and the fixed version. The issue was reported by a researcher and verified by the vendor. The vendor has provided a patch to address this vulnerability. Users of affected versions should update to the latest version to prevent potential exploitation. The CVE record and NVD page also provide additional references for further information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.