Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach GHES upload endpoint over network
-
DeliveryInject path-traversal into request parameter
-
ExploitRedirect internal API call (SSRF)
-
ExecutionReach internal-only service
-
ImpactExpose sensitive credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to the GitHub Enterprise Server upload endpoint and does not require authentication or user interaction (PR:N/UI:N), and applies to default configurations of all GHES versions prior to 3.22. The concrete prerequisite is the ability to inject path-traversal content into the upload endpoint's request parameters to break out of the intended request flow and redirect an internal API call. Limiting factors per the CVSS 4.0 vector are high attack complexity (AC:H) and a present attack requirement (AT:P), meaning the attacker must satisfy conditions beyond simply reaching the endpoint for the SSRF to succeed; meaningful credential exposure further depends on the targeted internal services actually being reachable from the appliance, so instances with restricted egress or network segmentation present a harder target. |
| Impact | Signals are mixed and should be weighed rather than taken at face value. CVSS 4.0 rates this 9.2 Critical with a network attack vector (AV:N) and no privileges or user interaction required (PR:N/UI:N), and full high impact to confidentiality, integrity, and availability of the vulnerable system (VC:H/VI:H/VA:H) - explaining the high score and the credential-exposure concern. However, the same vector sets high attack complexity (AC:H) and a present attack requirement (AT:P), meaning successful exploitation depends on conditions outside the attacker's control rather than being a trivial one-shot request; subsequent-system impact is rated none (SC:N/SI:N/SA:N), so the scored impact is confined to the GHES system itself even though SSRF could practically enable further internal pivoting. There is no CISA KEV listing and no public exploit identified, so this is not currently known to be actively exploited or weaponized. EPSS was not provided and cannot be cited. On balance this is a genuine high priority for internet-reachable or widely-accessible GHES instances given unauthenticated network reach and credential exposure, but AC:H/AT:P suggest exploitation is non-trivial rather than mass-automatable; prioritize patching but recognize the barrier to reliable exploitation. |
| Exploit ScenarioDerived | An attacker with network reachability to a GitHub Enterprise Server instance sends a crafted request to the vulnerable upload endpoint, embedding path-traversal content in a request parameter to redirect an internal API call. The appliance then issues that request to an internal service the attacker could not otherwise reach, potentially returning sensitive credentials. No authentication is required (PR:N), but the high complexity and attack requirement (AC:H/AT:P) mean the attacker must satisfy specific conditions to make the redirection succeed; no public proof-of-concept is currently identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 27, 2026
Server-side request forgery in GitHub Enterprise Server lets an unauthenticated attacker coerce the appliance into issuing crafted requests to internal services, reachable through an upload endpoint that fails to validate input. By injecting path-traversal content into request parameters, an attacker can redirect internal API calls to reach back-end services and harvest sensitive credentials. No public exploit identified at time of analysis; the issue was reported through the GitHub Bug Bounty program and carries a CVSS 4.0 base score of 9.2 (Critical), though the vector flags high attack complexity and an extra attack requirement that temper real-world ease of exploitation.
RemediationAI
Upgrade GitHub Enterprise Server to a fixed release on your current line: Vendor-released patches are 3.16.20, 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.1 - apply the patch matching your deployed series (release notes at https://docs.github.com/en/enterprise-server@3.16/admin/release-notes#3.16.20 and the equivalent 3.17/3.18/3.19/3.20/3.21 pages). If an immediate upgrade is not possible, reduce exposure with compensating controls: restrict network access to the GHES management/web endpoints to trusted networks or a VPN so the unauthenticated upload endpoint is not reachable from untrusted clients (trade-off: may break external integrations and remote contributor access), and place egress filtering on the appliance so it cannot initiate requests to sensitive internal hosts, metadata services, or credential stores (trade-off: can disrupt legitimate outbound integrations such as webhooks, package proxies, and external auth). Monitor appliance and reverse-proxy logs for anomalous upload requests containing path-traversal sequences and unexpected internal-bound requests. These mitigations narrow the attack surface but do not replace the patch.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GitHub Enterprise Server is the self-hosted, on-premises distribution of GitHub used by organizations to run private code, CI, and collaboration on their own infrastructure (CPE cpe:2.3:a:github:enterprise_server). The root-cause class is CWE-918 (Server-Side Request Forgery): an upload endpoint accepts attacker-controlled values that are used to construct the destination of a server-initiated request without adequate validation. The vendor and tags indicate the SSRF is reached specifically via path traversal (e.g., '../' style sequences) embedded in request parameters, which lets the attacker break out of the intended request flow and steer internal API calls. Because the request originates from the appliance itself, it can reach internal-only services and metadata/credential endpoints that are not exposed to the public network - the classic SSRF pivot into a trusted internal perimeter.
Know when Github gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Primary rating from Vendor (GitHub_P) · only source for this CVE.
CVSS VectorVendor: GitHub_P
Lifecycle Timeline
3DescriptionCVE.org
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.16.20, 3.17.17, 3.18.11, 3.19.8, 3.20.4, and 3.21.1. This vulnerability was reported via the GitHub Bug Bounty program.
Executive ViewAI
GitHub Enterprise Server is vulnerable to an unauthenticated server-side request forgery attack (CVE-2026-9312, CVSS 9.2) that allows attackers to access internal services and harvest credentials without a patch currently available. Organizations running GHES on premise are at risk of credential compromise affecting their entire development infrastructure. Immediate compensating controls are required to protect sensitive systems until a vendor patch is released.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict network access from GHES to internal backend services using firewall rules; (2) Implement WAF or reverse-proxy rules to block path-traversal sequences in upload endpoint requests; (3) Enable enhanced logging and alerting on internal service access from GHES appliance; (4) Rotate credentials for internal services accessible from GHES; (5) Isolate GHES network segment from production systems if operationally feasible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Supply chain vulnerability in Eclipse Theia GitHub Actions workflow. The preview.yml workflow uses pull_request_target w
Supply chain attack vector in OpenLIT GitHub Actions workflows. The pull_request_target trigger with checkout enables ma
Eigent multi-agent workflow CI pipeline (ci.yml) uses pull_request_target with checkout of untrusted PR code, enabling a
An unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. R
cmark-gfm is GitHub's extended version of the C reference implementation of CommonMark. Rated critical severity (CVSS 9.
An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowe
Unauthenticated infrastructure overwrite in Hoppscotch API development ecosystem before 2026.2.0. Attackers can overwrit
A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCrede
OneUptime versions prior to 10.0.19 allow unauthenticated attackers to hijack GitHub App integrations across projects by
PolarLearn versions 0-PRERELEASE-15 and earlier lack proper state parameter validation in OAuth 2.0 authentication, enab
Path traversal in esm.sh CDN prior to version 0.0.0-20260116051925-c62ab83c589e allows unauthenticated remote attackers
actions/artifact is the GitHub ToolKit for developing GitHub Actions. Rated high severity (CVSS 7.5), this vulnerability
EUVD-2026-32027
GHSA-fwfp-h68w-2hcr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB