CVE-2026-3854: Remote Code Execution via Git Push Metadata Injection in GitHub Enterprise Server
- Vendor
- GitHub
CVE-2026-3854 is a remote code execution vulnerability in GitHub Enterprise Server's server-side Git push pipeline. Client-controlled push option values were embedded into semicolon-delimited internal X-Stat metadata without adequate sanitization. An authenticated attacker with repository push access could inject additional fields, with last-write-wins parsing allowing attacker-controlled values to override trusted execution settings. Downstream hook processing trusted these settings, enabling manipulation of the execution environment and hook resolution to bypass sandboxing and execute arbitrary commands as the git service user. The underlying vulnerability also affected GitHub-hosted services, which were patched centrally.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary command execution outside the normal hook sandbox as the git service user, not directly as root. This account can access repository data, internal configuration, and service secrets, potentially allowing repository disclosure or modification beyond the attacker's authorized repository and broader compromise of the affected Enterprise Server instance. On shared GitHub-hosted infrastructure, the vulnerability created potential cross-tenant repository exposure. GitHub stated that its investigation found no evidence of malicious exploitation beyond researcher testing.
Mitigation
If you can’t patch tonight, do this now.
Review audit logs for Git push operations with semicolons in push option values, correlating matches with the initiating account, repository, source address, and timestamp. A semicolon alone is not proof of exploitation. Investigate associated unusual process execution, filesystem access, and repository activity. If exploitation is suspected, preserve relevant logs and system state, initiate incident response, and rotate potentially exposed credentials and internal secrets. These detection and response measures do not replace upgrading.
Remediation
Patch, then assume compromise.
Upgrade GitHub Enterprise Server to a fixed release: 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, or a later patched release in the applicable branch; version 3.20.0 also includes the fix. GitHub-hosted services were patched centrally and require no customer patch deployment. The underlying correction sanitizes user-controlled push options before incorporating them into internal metadata.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 7 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-3854 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-3854 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-3854?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-3854, the earliest disclosed Apr 29, 2026.
- Is there a patch for CVE-2026-3854?
- Upgrade GitHub Enterprise Server to a fixed release: 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, or a later patched release in the applicable branch; version 3.20.0 also includes the fix. GitHub-hosted services were patched centrally and require no customer patch deployment.
- What products are affected by CVE-2026-3854?
- GitHub Enterprise Server.
- How severe is CVE-2026-3854?
- CVE-2026-3854 has a CVSS v4 score of 8.7 (High) and an EPSS score of 41.9% (99th percentile) as of Nov 19, 2026.
Recent activity
261 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.