Description
An incorrect authorization vulnerability was identified in GitHub Enterprise Server that allowed an attacker to merge their own pull request into a repository without having push access by exploiting an authorization bypass in the enable_auto_merge mutation for pull requests. This issue only affected repositories that allow forking as the attack relies on opening a pull request from an attacker-controlled fork into the target repository. Exploitation was only possible in specific scenarios. It required a clean pull request status and only applied to branches without branch protection rules enabled. This vulnerability affected GitHub Enterprise Server versions prior to 3.19.2, 3.18.5, and 3.17.11, and was fixed in versions 3.19.2, 3.18.5, and 3.17.11. This vulnerability was reported via the GitHub Bug Bounty program.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| GitHub | Enterprise Server | 3.17.0 – < 3.17.11, 3.18.0 – < 3.18.5, 3.19.0 – < 3.19.2 | 3.17.11 |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
GitHub 2 repositories
-
manoelprovider20-lgtm/merge-authz-test ★ 0 · Jul 18, 2026
authz test (CVE-2026-1999 siblings)
-
jwde/automerge-test ★ 0 · Mar 15, 2026
Testing auto-merge CVE-2026-1999 variant
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Advisories 2
- NCSC-2026-0067 Kwetsbaarheden verholpen in GitHub Enterprise Server NCSC-NL (Netherlands) · Feb 20, 2026
- WID-SEC-2026-0460 Microsoft GitHub Enterprise Server: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen BSI CERT-Bund (WID) · Feb 18, 2026