SECUFOCUSNOW
Home›CVE index›CVE-2026-9312
Review reviewCritical

CVE-2026-9312

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...

CVSS
9.2
EPSS
6.55%
93.0% percentile
CISA KEV
Not listed
Published
2026.05.27
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability6.55%
Technical severityCVSS 9.2

Vulnerability overview

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...

Affected product and versions

Product
GitHub Enterprise Server, enterprise server
Affected versions
>= 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
Fixed versions
3.16.19, 3.17.16, 3.18.10, 3.19.7, 3.20.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that GitHub Enterprise Server, enterprise server and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CWE
CWE-918