Remote code execution via git push option injection in GitHub Enterprise Server

Summary

An improper neutralization of special elements vulnerability was identified in GitHub Enterprise Server that allowed an attacker with push access to a repository to achieve remote code execution on the instance. During a git push operation, user-supplied push option values were not properly sanitized before being included in internal service headers. Because the internal header format used a delimiter character that could also appear in user input, an attacker could inject additional metadata fields through crafted push option values. This vulnerability was reported via the GitHub Bug Bounty program and has been fixed in GitHub Enterprise Server versions 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7 and 3.19.4.

Timeline

1. Mar 10, 2026, 5:37 PM UTCCVE published
2. Apr 28, 2026, 12:00 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Apr 29, 2026, 3:55 AM UTCRecord last updated
4. Oct 28, 2026EPSS reached 10%

   FIRST estimates at least a 10% chance of exploitation in the next 30 days

Affected versions

• GitHub Enterprise Server

  From 3.14.0 · through 3.14.24; From 3.15.0 · through 3.15.19; From 3.16.0 · through 3.16.15; From 3.17.0 · through 3.17.12; From 3.18.0 · through 3.18.6; From 3.19.0 · through 3.19.3

References 13