CVE-2026-9312 remediation guide
GitHub Enterprise Server, 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...
Identify the affected asset
Confirm whether GitHub Enterprise Server, enterprise server is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 3.16.0 <= 3.16.19, >= 3.17.0 <= 3.17.16, >= 3.18.0 <= 3.18.10, >= 3.19.0 <= 3.19.7, >= 3.20.0 <= 3.20.3, >= 3.21.0 < 3.21.1, >= 3.16.0 < 3.16.19, >= 3.17.0 < 3.17.16, >= 3.18.0 < 3.18.10, >= 3.19.0 < 3.19.7, >= 3.20.0 < 3.20.3, 3.21.1. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 3.16.19, 3.17.16, 3.18.10, 3.19.7, 3.20.3. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.