Skip to main content
CVE-2026-116643VulnerabilityPublished

GitHub Enterprise Server allowed an authenticated · SSH Certificate Authentication Bypass Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116643· High 8.6

Not known to be exploited · CVSS 8.6 High · fixed in 3.22.5 : patch Enterprise Server soon.

Data as of 18 Nov 2026, 05:18 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_P)CVSS 4.08.6
Patch
Available – fixed in 3.22.5, 3.21.10, 3.20.12 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Enterprise Server to 3.22.5, 3.21.10, 3.20.12 or 3.19.16.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.22.0 <3.22.5
Fixed in
  • 3.22.5
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.10
Fixed in
  • 3.21.10
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.12
Fixed in
  • 3.20.12
GitHubEnterprise ServerAffected
  • >=3.19.0 <3.19.16
Fixed in
  • 3.19.16

AI-suggested

Upgrade GitHub Enterprise Server to one of the fixed versions: 3.19.16, 3.20.12, 3.21.10, or 3.22.5, or any later release. This vulnerability is not present in versions 3.23 and later. No additional mitigations are indicated by the vendor advisory.

Description

A vulnerability in GitHub Enterprise Server prior to version 3.23 allowed an authenticated organization member to bypass SSH certificate authentication and access another user's private repositories. Exploitation required the use of built-in authentication and a valid SSH certificate issued by a trusted certificate authority. The issue was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5.

References

Community reviews

Loading reviews…