CVE-2026-6736: CWE-306 Missing Authentication for Critical Function in GitHub Enterprise Server
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.
AI Analysis
Technical Summary
An authentication bypass vulnerability (CWE-306) exists in GitHub Enterprise Server versions before 3.21. When external authentication providers are enabled, the signup endpoint fails to enforce authentication restrictions, allowing unauthenticated attackers to create local user accounts and establish sessions without identity provider validation. The vulnerability requires network access to the affected GHES instance. The created accounts are limited to default base permissions. GitHub fixed this issue in versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18.
Potential Impact
An attacker with network access to a vulnerable GitHub Enterprise Server instance can bypass external authentication controls to create local user accounts with default base permissions. This could allow unauthorized access to the instance with limited privileges, potentially enabling further reconnaissance or privilege escalation depending on the environment and configuration.
Mitigation Recommendations
This vulnerability is fixed in GitHub Enterprise Server versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18. Users should upgrade to one of these fixed versions or later to remediate the issue. Since this is an on-premises product, patching the affected instances is required. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.
CVE-2026-6736: CWE-306 Missing Authentication for Critical Function in GitHub Enterprise Server
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
An authentication bypass vulnerability (CWE-306) exists in GitHub Enterprise Server versions before 3.21. When external authentication providers are enabled, the signup endpoint fails to enforce authentication restrictions, allowing unauthenticated attackers to create local user accounts and establish sessions without identity provider validation. The vulnerability requires network access to the affected GHES instance. The created accounts are limited to default base permissions. GitHub fixed this issue in versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18.
Potential Impact
An attacker with network access to a vulnerable GitHub Enterprise Server instance can bypass external authentication controls to create local user accounts with default base permissions. This could allow unauthorized access to the instance with limited privileges, potentially enabling further reconnaissance or privilege escalation depending on the environment and configuration.
Mitigation Recommendations
This vulnerability is fixed in GitHub Enterprise Server versions 3.20.2, 3.19.6, 3.18.9, 3.17.15, and 3.16.18. Users should upgrade to one of these fixed versions or later to remediate the issue. Since this is an on-premises product, patching the affected instances is required. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_P
- Date Reserved
- 2026-04-21T02:53:28.704Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fd029ecbff5d861038a136
Added to database: 5/7/2026, 9:22:38 PM
Last enriched: 5/7/2026, 9:37:25 PM
Last updated: 5/7/2026, 10:37:35 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.