GitHub Enterprise Server SSH certificate bypass lets org members read private repos (CVE-2026-116643)
NIST's National Vulnerability Database has published CVE-2026-116643, an SSH certificate authentication bypass in GitHub Enterprise Server. An authenticated organization member can read and modify other users' private repositories. The record rates it HIGH (CVSS 4.0 8.6) and lists fixed builds for four release lines. No exploitation has been reported in the source material.
NIST's National Vulnerability Database has published CVE-2026-116643, describing an SSH certificate authentication bypass in GitHub Enterprise Server. According to the record, an authenticated organization member could read and modify another user's private repositories within the scope of a trusted SSH certificate authority. [1]
The record says exploitation needs an instance that uses built-in authentication, plus a valid certificate issued to the attacker by a trusted SSH certificate authority. Administrators who do not use built-in authentication may fall outside the described conditions, though the source does not say so explicitly. [1]
The affected range is supported releases before 3.23. The record lists fixed versions 3.19.16, 3.20.12, 3.21.10 and 3.22.5. The CVSS 4.0 score of 8.6 is attributed to the record's CNA, GitHub's product security contact. [1]
The vulnerability was reported through GitHub's Bug Bounty program, according to the record. The record does not say whether any exploitation has been observed. [1]
What we couldn't confirm
- No GitHub-published advisory or blog post was included in the source material; the details rely on the NVD record.
- The source does not state whether GitHub Enterprise Server 3.23 or later is fixed, only that releases before 3.23 are affected.
- No exploitation status is stated in the source; it is recorded as unknown.
- The source does not give a publication or release date for the fixed builds.
- No CVSS 3.x score or vector is provided, only the CVSS 4.0 score.
- The number of affected instances or customers is not known.
- The source does not describe what 'trusted SSH certificate authority' scope means in practice or how administrators can check their configuration.
- The record does not say whether any independent researcher or third party has confirmed the issue beyond the NVD entry.
Sources
- NIST National Vulnerability Database: CVE-2026-116643: An SSH certificate authentication bypass vulnerability in GitHub Enterprise Server allowed an authenticated organization member to read and modify another user'Source published · TechDots found it
Statements labelled as a company's claim have not been independently confirmed by TechDots.
Get Cybersecurity stories by email
Related coverage
nginx2root: five new nginx bugs, patch now and lock origins to Cloudflare
F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, 2026. Five memory corruption flaws, named nginx2root by Xint, can crash workers or run commands, and one HTTP/2 bug is the most widespread. Cloudflare says its edge is unaffected and that its proxy shields origins from the HTTP/2 and HTTP/3 attacks, but patching is still required.
Etherpad pre-auth file read flaw rated critical in GitHub advisory
GitHub Advisory Database has published an advisory for an unauthenticated file-read flaw in Etherpad's /static/* handler, affecting ep_etherpad-lite versions 1.8.14 up to 3.3.3 and fixed in 3.3.3. The advisory rates it critical, CVSS 9.8.