CVE-2026-116643: SSH certificate authentication bypass in GitHub Enterprise Server
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: GitHub Enterprise Server 3.19.*, 3.19.16, 3.20.*.
Low priority for now. Upgrade to GitHub Enterprise Server 3.19.*, 3.19.16, 3.20.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 18, 2026
- Updated
- Nov 18, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-289
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_P
- 8.6
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.
GitHub Enterprise Server
- 3.19.0 and later · before 3.19.*affected · semverfixed in 3.19.16
- 3.20.0 and later · before 3.20.*affected · semverfixed in 3.20.12
- 3.21.0 and later · before 3.21.*affected · semverfixed in 3.21.10
- 3.22.0 and later · before 3.22.*affected · semverfixed in 3.22.5
Same product
github: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection61This week
- CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server55Plan
- CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server47Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-110307Nov 18, 2026 · Incorrect authorization vulnerability in GitHub Enterprise Server allowed unauthorized control of enterprise-owned GitHub Apps via user and enterprise ID…29Monitor
- ← EarlierCVE-2026-116637Nov 18, 2026 · Improper link resolution in GitHub Enterprise Server allowed root-level file modification via pre-receive hook environments34Monitor
- Later →CVE-2026-131647Nov 18, 2026 · Improper neutralization of CRLF sequences in GitHub Enterprise Server allowed branch protection bypass via pull request conflict resolution21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GitHub Enterprise Server | 3.19.* | Vendor (CNA) |
| GitHub Enterprise Server | 3.19.16 | Vendor (CNA) |
| GitHub Enterprise Server | 3.20.* | Vendor (CNA) |
| GitHub Enterprise Server | 3.20.12 | Vendor (CNA) |
| GitHub Enterprise Server | 3.21.* | Vendor (CNA) |
| GitHub Enterprise Server | 3.21.10 | Vendor (CNA) |
| GitHub Enterprise Server | 3.22.* | Vendor (CNA) |
| GitHub Enterprise Server | 3.22.5 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 19, 2026+2 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Tawfik Zoubayr (toofikz)finder
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-9689043 days apartServer-Side Request Forgery vulnerability was identified in GitHub Enterprise Server that allowed requests to attacker-controlled internal hosts34Monitor
- CVE-2026-1127400 days apartOS command injection in GitHub Enterprise Server allowed command execution as the host git user on peer cluster nodes30Monitor
- CVE-2026-1318200 days apartServer-side request forgery in GitHub Enterprise Server enabled remote code execution via Slack webhook validity checks30Monitor
- CVE-2026-10460815 days apartUse-after-free vulnerability in GitHub Enterprise Server allowed remote code execution in the Git service30Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: patch commit or PR link.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-289 · Authentication Bypass by Alternate NameCVSS vector
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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.