Skip to main content
CVE-2026-131647VulnerabilityPublished

GitHub Enterprise Server · CRLF Injection Vulnerability Was Identified

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131647· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 3.22.5 : update Enterprise Server when convenient.

Data as of 18 Nov 2026, 05:19 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_P)CVSS 4.05.3
Patch
Available – fixed in 3.22.5, 3.21.10, 3.20.12 +1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Enterprise Server to 3.22.5, 3.21.10, 3.20.12 or 3.19.16.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.22.0 <3.22.5
Fixed in
  • 3.22.5
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.10
Fixed in
  • 3.21.10
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.12
Fixed in
  • 3.20.12
GitHubEnterprise ServerAffected
  • >=3.19.0 <3.19.16
Fixed in
  • 3.19.16

AI-suggested

Apply the official patches available in GitHub Enterprise Server versions 3.19.16, 3.20.12, 3.21.10, or 3.22.5 and later. Upgrading to version 3.23 or newer will also resolve this vulnerability. No additional mitigation steps are indicated by the vendor.

Description

A CRLF injection vulnerability in GitHub Enterprise Server allowed users with write access to bypass branch protections and update branches or tags via specially crafted input during pull request conflict resolution. This issue affected all versions prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. The vulnerability was responsibly disclosed through the GitHub Bug Bounty program.

References

Community reviews

Loading reviews…