Quick answers
- Is CVE-2026-96890 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96890 being exploited in the wild.
- How severe is CVE-2026-96890?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- GitHub Enterprise Server 3.20, 3.21, 3.22.
- Is there a fix for CVE-2026-96890?
- Yes: fixed in Enterprise Server 3.20.9, 3.21.7, 3.22.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96890 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-96890?
- Check whether you run GitHub Enterprise Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Enterprise Server 3.20.9, 3.21.7, 3.22.2
Technical details
The secret scanning validator for GCP service account credentials trusts the token endpoint embedded in a committed credential without restricting the destination, allowing SSRF attacks. Exploitation requires an authenticated user with repository push permissions on an instance with GitHub Advanced Security and secret scanning validity checks enabled. A successful attack can chain the SSRF to achieve remote code execution on the appliance.
Affected products
- GitHub Enterprise Server 3.20, 3.21, 3.22
Timeline
- 2026-10-06: disclosed