CVE-2026-116643 json
SSH certificate authentication bypass in GitHub Enterprise Server
published 1h ago modified 1h ago also EUVD-2026-128408
- cvss
- 8.6
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
An SSH certificate authentication bypass vulnerability in GitHub Enterprise Server allowed an authenticated organization member to read and modify another user's private repositories within the trusted certificate authority's scope. Exploitation required an instance using built-in authentication and a valid certificate issued to the attacker by a trusted SSH certificate authority. This vulnerability affected supported GitHub Enterprise Server releases prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program.
Patch / fix
- GitHub Enterprise Server 3.19.16, 3.20.12, 3.21.10, 3.22.5
Is CVE-2026-116643 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.6 | 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 |
| CNA | 4.0 | 8.6 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- GitHub Enterprise Server
Classification
- Weakness
-
- CWE-289 Authentication Bypass by Alternate Name
References
-
docs.github.com
/en/enterprise-server@3.19/admin/release-notes#3.19.16
release-notes
-
docs.github.com
/en/enterprise-server@3.20/admin/release-notes#3.20.12
release-notes
-
docs.github.com
/en/enterprise-server@3.21/admin/release-notes#3.21.10
release-notes
-
docs.github.com
/en/enterprise-server@3.22/admin/release-notes#3.22.5
release-notes
Sources
- CVE List CVE-2026-116643
- NVD CVE-2026-116643
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.