CVE-2026-96890: Server-Side Request Forgery vulnerability was identified in GitHub Enterprise Server that allowed requests to attacker-controlled internal hosts

Published Oct 6, 2026
·
Updated

A Server-Side Request Forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed a repository contributor to cause the appliance to issue requests to attacker-controlled internal hosts, which could be chained to achieve remote code execution on the appliance. The secret scanning validator for GCP service account credentials trusted the token endpoint embedded in a committed credential and issued a request to it without restricting the destination. Exploitation required an authenticated user with permission to push to a repository on an instance with GitHub Advanced Security and secret scanning validity checks enabled, a non-default configuration. This vulnerability affected GitHub Enterprise Server 3.20, 3.21, and 3.22 and was fixed in versions 3.20.9, 3.21.7, and 3.22.2. This vulnerability was reported through the GitHub Bug Bounty program.

Affected Software

1 affected component
GitHub Enterprise Server>=3.20.0<3.20.9, >=3.21.0<3.21.7, >=3.22.0<3.22.2

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.20.9
  2. Upgrade

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

    Fixed in 3.21.7
  3. Upgrade

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

    Fixed in 3.22.2

Event History

Oct 6, 2026
CVE Published
via MITRE·06:56 PM
Data Sourced
via MITRE·06:56 PM
DescriptionWeakness
Data Sourced
via NVD·07:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Only GitHub Enterprise Server instances running 3.20, 3.21, or 3.22 with GitHub Advanced Security and secret scanning validity checks enabled are affected. The required secret-scanning configuration is non-default.

2

What access does an attacker need?

An attacker needs an authenticated account with permission to push to a repository on the affected instance. They can commit GCP service account credentials containing an attacker-controlled token endpoint, causing the appliance to request an internal host.

3

How serious is successful exploitation?

The SSRF can be chained to achieve remote code execution on the appliance. The CVSS 4.0 score is 8.7 (High), with high impacts to confidentiality, integrity, and availability.

4

Which versions fix the issue?

Upgrade affected 3.20 installations to 3.20.9, 3.21 installations to 3.21.7, or 3.22 installations to 3.22.2.

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