CVE-2026-111044

waiting for further signalsZero needs more public information before it can validate it.

GHSA-6jvv-jqr7-m6m3 ↗EUVD-2026-103189 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
LizardByte Sunshine >= 2026.329.165800
fixed in v2026.906.222525
CWE-863 Incorrect Authorization
ETK-2026-1830Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 13h 14msince last run
1h 04mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h25m
0
+2h
+6h
+8h
+10h
+12h

description

Sunshine versions 2026.329.165800 through before 2026.906.222525 can fail to enforce disabled paired-client identities during certificate authentication. A previously paired client that retains its private key may authenticate despite being disabled, potentially regaining access; clients that were never paired are not affected.

mitigation

Upgrade Sunshine to version 2026.906.222525 or later. Until upgrading, remove paired clients whose access must be revoked to remove their trust relationship.

fixed in v2026.906.222525

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.16%4th percentile
agent run time
1h 04m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 21:59Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-16 21:59Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-111044

{
  "etk_id": "ETK-2026-1830",
  "cve_id": "CVE-2026-111044",
  "display_id": "CVE-2026-111044",
  "ghsa_id": "GHSA-6jvv-jqr7-m6m3",
  "euvd_id": "EUVD-2026-103189",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Certificate authorization bypass in Sunshine",
  "summary": "Sunshine versions 2026.329.165800 through before 2026.906.222525 can fail to enforce disabled paired-client identities during certificate authentication. A previously paired client that retains its private key may authenticate despite being disabled, potentially regaining access; clients that were never paired are not affected.",
  "mitigation": "Upgrade Sunshine to version 2026.906.222525 or later. Until upgrading, remove paired clients whose access must be revoked to remove their trust relationship.",
  "vendor": "LizardByte",
  "product": "Sunshine",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2026.329.165800"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "v2026.906.222525"
      ],
      "package_name": "LizardByte/Sunshine",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 7.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L",
  "epss_score": 0.0016,
  "epss_percentile": 0.0449,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 64.48752805,
  "t0_at": "2026-10-16T21:59:00.939000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T21:59:00.939000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T21:59:00.939000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111044"
    }
  }
}

published 2026-10-17 01:19Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.