CVE-2026-6736: Authentication bypass vulnerability in GitHub Enterprise Server allowed creation of local user accounts bypassing the configured external identity provider

Published May 7, 2026
·
Updated

An authentication bypass vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to create a local user account, bypassing the configured external identity provider. When external authentication was enabled, the signup endpoint did not properly enforce the authentication restriction, allowing account creation and session establishment without identity provider validation. The created account was limited to the default base permissions configured on the instance. Exploitation required network access to a GHES instance configured with an external authentication provider. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18.

Affected Software

6 affected components
GitHub GitHub Enterprise Server<3.21
GitHub Enterprise Server<3.16.18
GitHub Enterprise Server>=3.17.0<3.17.15
GitHub Enterprise Server>=3.18.0<3.18.9
GitHub Enterprise Server>=3.19.0<3.19.6
GitHub Enterprise Server>=3.20.0<3.20.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.20.2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.19.6
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.18.9
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.17.15
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.16.18

Event History

May 7, 2026
CVE Published
via MITRE·09:14 PM
Data Sourced
via MITRE·09:14 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
May 30, 58331
Event
via FIRST·11:40 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-6736?

CVE-2026-6736 has been classified with a critical severity level due to the potential for unauthenticated access to create local user accounts.

2

How do I fix CVE-2026-6736?

To remediate CVE-2026-6736, upgrade GitHub Enterprise Server to version 3.21 or later, where the vulnerability is resolved.

3

What impact does CVE-2026-6736 have on GitHub Enterprise Server?

CVE-2026-6736 allows attackers to bypass authentication mechanisms and create unauthorized user accounts.

4

Is CVE-2026-6736 present in earlier versions of GitHub Enterprise Server?

Yes, CVE-2026-6736 affects GitHub Enterprise Server versions up to 3.21 but is fixed in later versions.

5

Can CVE-2026-6736 be exploited remotely?

Yes, CVE-2026-6736 can be exploited remotely by unauthenticated attackers, making it a significant security risk.

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