CVE-2026-131647 json
Improper neutralization of CRLF sequences in GitHub Enterprise Server allowed branch protection bypass via pull request conflict resolution
published 1h ago modified 1h ago also EUVD-2026-128413
- cvss
- 5.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- GitHub Enterprise Server 3.19.16, 3.20.12, 3.21.10, 3.22.5
Is CVE-2026-131647 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- GitHub Enterprise Server
Classification
- Weakness
-
- CWE-93 Improper Neutralization of CRLF Sequences
References
-
docs.github.com
/en/enterprise-server@3.19/admin/release-notes#3.19.16
release-notes
-
docs.github.com
/en/enterprise-server@3.20/admin/release-notes#3.20.12
release-notes
-
docs.github.com
/en/enterprise-server@3.21/admin/release-notes#3.21.10
release-notes
-
docs.github.com
/en/enterprise-server@3.22/admin/release-notes#3.22.5
release-notes
Sources
- CVE List CVE-2026-131647
- NVD CVE-2026-131647
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.