CVE
GitHub Enterprise Server authentication bypass in SSH certificate authentication
- Exploited
- No known exploitation
- Fix
- Fixed in 3.19.16, 3.20.12, 3.21.10, 3.22.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.19.16, 3.20.12, 3.21.10, 3.22.5.
Summary
GitHub Enterprise Server has an SSH certificate authentication bypass that lets a logged-in organization member read and modify another user's private repositories. An attacker can reach it remotely over the network with low-privilege login, but only on instances that use built-in authentication and where the attacker holds a valid certificate from a trusted SSH certificate authority.
Original description
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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.19.16, 3.20.12, 3.21.10, 3.22.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-116643 (SSH certificate authentication bypass in GitHub Enterprise Server), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-116643 (entry last updated 2026-11-18):
Affected:
- GitHub Enterprise Server: from 3.19.0, fixed in 3.19.16; from 3.20.0, fixed in 3.20.12; from 3.21.0, fixed in 3.21.10; from 3.22.0, fixed in 3.22.5
Fixed versions: 3.19.16, 3.20.12, 3.21.10, 3.22.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116643 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116643 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.16
- https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.12
- https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.10
- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-116643
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116643"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- GitHub Enterprise Server
From 3.19.0 · fixed in 3.19.16; From 3.20.0 · fixed in 3.20.12; From 3.21.0 · fixed in 3.21.10; From 3.22.0 · fixed in 3.22.5
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-116643 |
| Record | NVD · CVE-2026-116643 |
| Other links 4 | |
| Link | docs.github.com · en/enterprise-server@3.19/admin/release-notes#3.19.16 |
| Link | docs.github.com · en/enterprise-server@3.20/admin/release-notes#3.20.12 |
| Link | docs.github.com · en/enterprise-server@3.21/admin/release-notes#3.21.10 |
| Link | docs.github.com · en/enterprise-server@3.22/admin/release-notes#3.22.5 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116643
Is CVE-2026-116643 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-116643?
Enterprise Server: from 3.19.0 before 3.19.16; from 3.20.0 before 3.20.12; from 3.21.0 before 3.21.10; from 3.22.0 before 3.22.5.Source: cve.now feed data
How do I fix CVE-2026-116643?
Upgrade to a fixed version: 3.19.16, 3.20.12, 3.21.10, 3.22.5.Source: cve.now feed data