CVE-2026-3854
Improper Neutralization in GitHub Enterprise Server Enables RCE
Publication date: 2026-03-10
Last updated on: 2026-04-28
Assigner: GitHub, Inc. (Products Only)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| github | enterprise_server | From 3.17.0 (inc) to 3.17.12 (exc) |
| github | enterprise_server | From 3.18.0 (inc) to 3.18.6 (exc) |
| github | enterprise_server | From 3.19.0 (inc) to 3.19.3 (exc) |
| github | enterprise_server | to 3.14.24 (exc) |
| github | enterprise_server | From 3.15.0 (inc) to 3.15.19 (exc) |
| github | enterprise_server | From 3.16.0 (inc) to 3.16.15 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
Can you explain this vulnerability to me?
This vulnerability is an improper neutralization of special elements in GitHub Enterprise Server. It allows an attacker who has push access to a repository to execute remote code on the server instance. The issue occurs because user-supplied push option values are not properly sanitized during a git push operation before being included in internal service headers. Since the internal header format uses a delimiter character that can also appear in user input, an attacker can inject additional metadata fields by crafting malicious push option values.
How can this vulnerability impact me? :
This vulnerability can have a severe impact as it allows an attacker with push access to execute arbitrary code remotely on the GitHub Enterprise Server instance. This could lead to unauthorized control over the server, potentially compromising the integrity, confidentiality, and availability of the system and its data.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update GitHub Enterprise Server to one of the fixed versions: 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6, or 3.19.3.