CVE-2026-9312: Server-Side Request Forgery vulnerability in GitHub Enterprise Server allowed access to internal services via path traversal in upload endpoint

Published May 27, 2026
·
Updated

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.

Affected Software

7 affected components
GitHub GitHub Enterprise Server<3.22
GitHub Enterprise Server>=3.16.0<3.16.19
GitHub Enterprise Server>=3.17.0<3.17.16
GitHub Enterprise Server>=3.18.0<3.18.10
GitHub Enterprise Server>=3.19.0<3.19.7
GitHub Enterprise Server>=3.20.0<3.20.3
GitHub Enterprise Server=3.21.1-rc1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.17.17
  2. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.18.11
  3. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.19.8
  4. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.20.4
  5. Upgrade

    Upgrade GitHub Enterprise Server to a version that resolves this vulnerability.

    Fixed in 3.21.2

Event History

May 27, 2026
CVE Published
via MITRE·12:02 AM
Data Sourced
via MITRE·12:02 AM
DescriptionWeakness
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeaknessAffected Software
Apr 28, 58520
Event
via FIRST·06:31 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-9312?

CVE-2026-9312 has a critical severity score of 9.2.

2

How do I fix CVE-2026-9312?

To fix CVE-2026-9312, update GitHub Enterprise Server to the latest version where the vulnerability has been patched.

3

What type of vulnerability is CVE-2026-9312?

CVE-2026-9312 is classified as a server-side request forgery (SSRF) vulnerability.

4

What attacks can be performed using CVE-2026-9312?

An attacker can exploit CVE-2026-9312 to send crafted requests to internal services through path traversal in the upload endpoint.

5

Who is affected by CVE-2026-9312?

Organizations using vulnerable versions of GitHub Enterprise Server are at risk from CVE-2026-9312.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203