CVE-2026-131647: Improper neutralization of CRLF sequences in GitHub Enterprise Server allowed branch protection bypass via pull request conflict resolution
A CRLF injection vulnerability was identified in GitHub Enterprise Server that allowed a user with write access to a repository to bypass branch protections and update branches or tags in that repository through specially crafted input when resolving pull request conflicts. This vulnerability affected all versions of GitHub Enterprise Server 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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.19.16 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.20.12 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.21.10 - Upgrade
Upgrade
GitHub Enterprise Serverto a version that resolves this vulnerability.Fixed in 3.22.5
Event History
Frequently Asked Questions
Who can exploit this vulnerability?
An attacker needs write access to the affected repository. The issue is triggered through specially crafted input while resolving pull request conflicts.
What protections can be bypassed?
A successful exploit can bypass branch protections and allow updates to branches or tags in the repository.
Which GitHub Enterprise Server versions need remediation?
All versions before 3.23 are affected. Fixes are available in 3.19.16, 3.20.12, 3.21.10, and 3.22.5.