GitHub Enterprise Server
Remote code execution via git push option injection in GitHub Enterprise Server
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.14.0, <= 3.14.24
- >= 3.15.0, <= 3.15.19
- >= 3.16.0, <= 3.16.15
- >= 3.17.0, <= 3.17.12
- >= 3.18.0, <= 3.18.6
- >= 3.19.0, <= 3.19.3
Fixed in 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4
Mitigation
Upgrade Enterprise Server to 3.14.25 or 3.15.20 or 3.16.16 or 3.17.13 or 3.18.7 or 3.19.4 or later.
Timeline
Days relative to CVE publicationFirst public PoC 49 days after publication; not in CISA KEV. First PoC: lysophavin18/CVE-2026-3854-PoC (created 29 Apr 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs · 1 pending · 4 informational · 1 suspicious or fake
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| lysophavin18/CVE-2026-3854-PoC | 29 Apr 2026 +49 d | 2 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| ridhinva/ghe-push-option-rce-scanner | 22 May 2026 +73 d | 0 | Pending · mkdir /quarantine/ridhinva__ghe-push-option-rce-scanner-a00d12180e30: permission denied |
Informational 4
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 5kr1pt/CVE-2026-3854 | 28 Apr 2026 +49 d | 0 | Informational · write-up |
| LACHHAB-Anas/Exploit_CVE-2026-3854 | 28 Apr 2026 +49 d | 0 | Informational · write-up |
| simondankelmann/cve-2026-3854-test | 29 Apr 2026 +50 d | 0 | Informational · detection |
| isagoakira/ghes-cve-scanner | 5 May 2026 +56 d | 0 | Informational · detection |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| royaleybovich/CVE-2026-3854-lab | 2 Aug 2026 +145 d | 9 | Suspicious · score 100
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.