CVE-2026-76851: CWE-918 Server-Side Request Forgery (SSRF) in GitHub Enterprise Server
Description
A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed remote code execution on the instance. Insufficient network isolation allowed malicious pre-receive hook code to impersonate an internal service and redirect trusted internal requests to a privileged service, leading to elevated code execution. Exploitation required pre-receive hook networking to be enabled and either site administrator privileges or write access to a repository containing a configured pre-receive hook. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.20, 3.18.14, 3.19.11, 3.20.7, and 3.21.5. This vulnerability was reported via the GitHub Bug Bounty program.
CVSS v4.0
Score 7.7high
Affected software
GitHub
Enterprise Server
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-76851 is a high-severity SSRF vulnerability (CWE-918) in GitHub Enterprise Server that permits remote code execution by abusing insufficient network isolation. Malicious pre-receive hook code can impersonate internal services and redirect trusted internal requests to privileged services, leading to elevated code execution privileges. Successful exploitation requires that pre-receive hook networking is enabled and that the attacker has site administrator privileges or write access to a repository with a configured pre-receive hook. The vulnerability affects all versions prior to 3.22 and was addressed by GitHub in versions 3.17.20, 3.18.14, 3.19.11, 3.20.7, and 3.21.5. The issue was reported through the GitHub Bug Bounty program. The CVSS 4.0 base score is 7.7, indicating high severity.
Potential Impact
An attacker with site administrator privileges or write access to a repository with a configured pre-receive hook can exploit this SSRF vulnerability to achieve remote code execution on the GitHub Enterprise Server instance. This can lead to elevated privileges and potentially full control over the affected server. The vulnerability leverages insufficient network isolation to redirect internal trusted requests to privileged services.
Mitigation Recommendations
This vulnerability has been fixed in GitHub Enterprise Server versions 3.17.20, 3.18.14, 3.19.11, 3.20.7, and 3.21.5. Users should upgrade to one of these fixed versions or later to remediate the issue. Ensure that pre-receive hook networking is carefully managed and restrict write access to repositories with configured pre-receive hooks to trusted users only.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_P
- Date Reserved
- 2026-08-19T21:26:22.221Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a974cb9acd9273b4942f39f
Added to database: 09/01/2026, 22:07:53 UTC
Last enriched: 09/07/2026, 13:58:57 UTC
Last updated: 10/16/2026, 06:48:19 UTC
Views: 128
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.