CVE-2026-111801

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

GHSA-3jh9-3h8f-hj56 ↗EUVD-2026-128359 ↗

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.
GitHub Enterprise Server >= 3.21.0, < 3.21.*; >= 3.22.0, < 3.22.*
fixed in 3.21.*, 3.22.*
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-4740Zero's internal tracking ID, independent of the CVE number., permanent identifier
16h 29msince 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+4h20m
0
+2h
+6h
+8h
+10h
+12h

description

GitHub Enterprise Server versions in the 3.21 and 3.22 series contain an authorization bypass in review-thread handling. A logged-in user who has an accessible repository and pull request as context may retrieve review-thread details from private repositories outside their authorized access when they know applicable thread identifiers.

mitigation

Upgrade Server to 3.21., 3.22. or later.

fixed in 3.21.*, 3.22.*

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.
–
agent run time
1h 04m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 01:04Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-18 01:04Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4740",
  "cve_id": "CVE-2026-111801",
  "display_id": "CVE-2026-111801",
  "ghsa_id": "GHSA-3jh9-3h8f-hj56",
  "euvd_id": "EUVD-2026-128359",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Review-thread authorization bypass in GitHub Enterprise Server",
  "summary": "GitHub Enterprise Server versions in the 3.21 and 3.22 series contain an authorization bypass in review-thread handling. A logged-in user who has an accessible repository and pull request as context may retrieve review-thread details from private repositories outside their authorized access when they know applicable thread identifiers.",
  "mitigation": "Upgrade Server to 3.21.*, 3.22.* or later.",
  "vendor": "GitHub",
  "product": "Enterprise Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.21.0, < 3.21.*",
        ">= 3.22.0, < 3.22.*"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.21.*",
        "3.22.*"
      ],
      "package_name": "Enterprise Server",
      "purl": null
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 64.32927663333334,
  "t0_at": "2026-11-18T01:04:41.938000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T01:04:41.938000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T01:04:41.938000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111801"
    }
  }
}

published 2026-11-18 01:51Z
last change 2026-11-18 21:43Z

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.