CVE-2026-5921: Server-Side Request Forgery in GitHub Enterprise Server allowed extraction of sensitive environment variables via timing side-channel attack
A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an attacker to extract sensitive environment variables from the instance through a timing side-channel attack against the notebook rendering service. When private mode was disabled, the notebook viewer followed HTTP redirects without revalidating the destination host, enabling an unauthenticated SSRF to internal services. By chaining this with regex filter queries against an internal API and measuring response time differences, an attacker could infer secret values character by character. Exploitation required that private mode be disabled and that the attacker be able to chain the instance's open redirect endpoint through an external redirect to reach internal services. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.21 and was fixed in versions 3.14.26, 3.15.21, 3.16.17, 3.17.14, 3.18.8, 3.19.5, and 3.20.1. This vulnerability was reported via the GitHub Bug Bounty program.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5921?
CVE-2026-5921 is classified as a critical severity vulnerability due to its potential for sensitive data exposure.
How do I fix CVE-2026-5921?
To mitigate CVE-2026-5921, update GitHub Enterprise Server to version 3.21 or later.
What does CVE-2026-5921 exploit?
CVE-2026-5921 exploits a server-side request forgery vulnerability allowing attackers to extract sensitive environment variables.
Which versions are affected by CVE-2026-5921?
CVE-2026-5921 affects GitHub Enterprise Server versions up to and including 3.20.
What impact does CVE-2026-5921 have on security?
CVE-2026-5921 can result in the unauthorized exposure of sensitive environment variables, compromising application security.