CVE-2024-0200: Unsafe Reflection RCE in GitHub Enterprise Server
- Vendor
- GitHub
CVE-2024-0200 is an unsafe reflection vulnerability in GitHub Enterprise Server and GitHub.com arising from use of a user-controlled identifier in a Ruby reflection call on a Repository object within the organizations actions settings flow. In the vulnerable path, the repository identifier key is derived from the rid_key request parameter and passed to a method that invokes repository.send without sufficient validation, enabling arbitrary invocation of accessible zero-argument methods, including methods with default arguments. The vulnerable rendering path returns the invoked method result in the repository items response. Researchers demonstrated impact by invoking a Repository method that traverses the Git RPC backend and returns process metadata containing the environment supplied to a spawned git process, thereby disclosing the Rails process environment. On GitHub Enterprise Server, the disclosed environment can include sensitive application secrets that enable further escalation to remote code execution. GitHub stated the issue affects GitHub Enterprise Server instances with GitHub Actions enabled and fixed it in 3.8.13, 3.9.8, 3.10.5, and 3.11.3; all versions prior to 3.12 were affected.
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 can disclose all environment variables available to the Rails process handling the request, including sensitive credentials, tokens, and application secrets. On GitHub.com, this resulted in exposure of numerous production secrets. On GitHub Enterprise Server, disclosure of secrets such as the enterprise session secret can be chained into forged Rails session cookies and unsafe deserialization, creating a path to remote code execution. The vulnerability therefore spans sensitive information disclosure and, in GHES deployments, potential full server compromise.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by limiting or disabling access to the affected organizations actions settings functionality to only strictly necessary administrators, and minimize the set of secrets and credentials present in the Rails process environment and inherited by spawned git processes. Review logs for anomalous requests to the repository items endpoint carrying unexpected rid_key values, and rotate potentially exposed secrets. Because exploitation requires elevated organizational privileges, enforcing least privilege for organization ownership reduces attack surface but does not eliminate the vulnerability.
Remediation
Patch, then assume compromise.
Upgrade GitHub Enterprise Server to a fixed release: 3.8.13, 3.9.8, 3.10.5, 3.11.3, or later supported versions. The underlying fix requires restricting the repository identifier selection to a safe allowlist rather than passing user-controlled values into reflective method dispatch. Where exposure may have occurred, rotate secrets that could have been present in the application environment, especially session-related secrets and credentials accessible to the Rails process.
Exploits
1 exploit validated by Mallory's analysis.
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-2024-0200 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2024-0200 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2024-0200?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2024-0200, the earliest disclosed Mar 18, 2024.
- Is there a patch for CVE-2024-0200?
- Upgrade GitHub Enterprise Server to a fixed release: 3.8.13, 3.9.8, 3.10.5, 3.11.3, or later supported versions. The underlying fix requires restricting the repository identifier selection to a safe allowlist rather than passing user-controlled values into reflective method dispatch.
- What products are affected by CVE-2024-0200?
- GitHub Enterprise Server.
- How severe is CVE-2024-0200?
- CVE-2024-0200 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 71.7% (99th percentile) as of Oct 16, 2026.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.