CVE-2026-116643: SSH certificate authentication bypass in GitHub Enterprise Server

Published Nov 18, 2026
·
Updated

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.

Affected Software

1 affected component
GitHub GitHub Enterprise Server<3.19.16, <3.20.12, <3.21.10, <3.22.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.19.16
  2. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.20.12
  3. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.21.10
  4. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.22.5

Event History

Nov 18, 2026
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
DescriptionWeakness
Data Sourced
via NVD·02:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to exploitation?

Exploitation required an instance using built-in authentication and a trusted SSH certificate authority. The attacker also needed a valid certificate issued by that trusted authority.

2

What access could an attacker gain?

An authenticated organization member could read and modify another user's private repositories within the trusted certificate authority's scope.

3

Which releases contain the fix?

The issue was fixed in GitHub Enterprise Server 3.19.16, 3.20.12, 3.21.10, and 3.22.5. Supported releases before 3.23 were affected.

4

How can we determine whether our instance is affected?

Check whether the instance runs a supported release before 3.23 and uses built-in authentication with a trusted SSH certificate authority. An instance meeting those conditions should be upgraded to the applicable fixed release.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203