CVE-2026-9312: CWE-918 Server-Side Request Forgery (SSRF) in GitHub Enterprise Server
A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to send crafted requests to internal services by exploiting insufficient input validation in an upload endpoint. By injecting path traversal content into request parameters, an attacker could bypass the intended request flow and redirect internal API calls, potentially accessing internal services and exposing sensitive credentials. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. This vulnerability was reported via the GitHub Bug Bounty program.
AI Analysis
Technical Summary
This vulnerability in GitHub Enterprise Server (CVE-2026-9312) involves SSRF via an upload endpoint with insufficient input validation. An unauthenticated attacker can inject path traversal sequences into request parameters to manipulate internal API calls, enabling access to internal services and exposure of sensitive credentials. The issue affects all versions before 3.22 and was addressed in versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. It was reported through the GitHub Bug Bounty program and carries a CVSS 4.0 score of 9.2, indicating critical severity.
Potential Impact
Successful exploitation allows unauthenticated attackers to perform SSRF attacks, redirecting internal API calls and potentially accessing internal services and sensitive credentials. This can lead to unauthorized information disclosure and compromise of internal infrastructure within affected GitHub Enterprise Server deployments.
Mitigation Recommendations
Fixes for this vulnerability are available in GitHub Enterprise Server versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. Users should upgrade affected versions (3.16.0, 3.17.0, 3.18.0, 3.19.0, 3.20.0, 3.21.0) to one of these patched releases or later. Patch status is confirmed by the vendor advisory. No additional mitigations are specified.
CVE-2026-9312: 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 an unauthenticated attacker to send crafted requests to internal services by exploiting insufficient input validation in an upload endpoint. By injecting path traversal content into request parameters, an attacker could bypass the intended request flow and redirect internal API calls, potentially accessing internal services and exposing sensitive credentials. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. This vulnerability was reported via the GitHub Bug Bounty program.
CVSS v4.0
Score 9.2critical
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in GitHub Enterprise Server (CVE-2026-9312) involves SSRF via an upload endpoint with insufficient input validation. An unauthenticated attacker can inject path traversal sequences into request parameters to manipulate internal API calls, enabling access to internal services and exposure of sensitive credentials. The issue affects all versions before 3.22 and was addressed in versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. It was reported through the GitHub Bug Bounty program and carries a CVSS 4.0 score of 9.2, indicating critical severity.
Potential Impact
Successful exploitation allows unauthenticated attackers to perform SSRF attacks, redirecting internal API calls and potentially accessing internal services and sensitive credentials. This can lead to unauthorized information disclosure and compromise of internal infrastructure within affected GitHub Enterprise Server deployments.
Mitigation Recommendations
Fixes for this vulnerability are available in GitHub Enterprise Server versions 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.2. Users should upgrade affected versions (3.16.0, 3.17.0, 3.18.0, 3.19.0, 3.20.0, 3.21.0) to one of these patched releases or later. Patch status is confirmed by the vendor advisory. No additional mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_P
- Date Reserved
- 2026-05-22T18:42:28.097Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a16385ae29bf47b5077ecbc
Added to database: 05/27/2026, 00:18:34 UTC
Last enriched: 06/30/2026, 23:43:08 UTC
Last updated: 07/12/2026, 04:15:13 UTC
Views: 623
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.