GitHub Enterprise Server up to 3.18.x/3.19.x/3.20.x/3.21.x Pull Request Conflict Resolution crlf injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in GitHub Enterprise Server up to 3.18.x/3.19.x/3.20.x/3.21.x. This vulnerability affects unknown code of the component Pull Request Conflict Resolution. Performing a manipulation results in crlf injection. This vulnerability is reported as CVE-2026-131647. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in GitHub Enterprise Server up to 3.18.x/3.19.x/3.20.x/3.21.x. This affects an unknown functionality of the component Pull Request Conflict Resolution. The manipulation with an unknown input leads to a crlf injection vulnerability. CWE is classifying the issue as CWE-93. The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs. This is going to have an impact on integrity. The summary by CVE is:
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.
It is possible to read the advisory at docs.github.com. This vulnerability is uniquely identified as CVE-2026-131647 since 11/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.19.16, 3.20.12, 3.21.10 or 3.22.5 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Crlf injectionCWE: CWE-93 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Enterprise Server 3.19.16/3.20.12/3.21.10/3.22.5
Timeline
11/17/2026 CVE reserved11/18/2026 Advisory disclosed
11/18/2026 VulDB entry created
11/18/2026 VulDB entry last update
Sources
Advisory: docs.github.comStatus: Confirmed
CNA: GitHub_P
CVE: CVE-2026-131647 (🔒)
GCVE (CVE): GCVE-0-2026-131647
GCVE (VulDB): GCVE-100-439167
Entry
Created: 11/18/2026 03:03Changes: 11/18/2026 03:03 (68)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.